Contract control history
TimelockController on Ethereum — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0x1dcc…f8c2 on Ethereum sits behind a 1d timelock. Gliese has recorded 4 control changes. Last checked 2026-09-09 19:46:02 UTC.
Timelock1d timelockEthereum
Current control surface
snapshot 2026-09-09 19:25:39 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call executedtimelock.call_executed | 2 | 0 |
| Call scheduledtimelock.call_scheduled | 2 | 0 |
| Total | 4 | 0 |
Recent changes
Setup-time events hidden- Call to 0xac69…64e8 scheduled, executable after 1dtimelock.call_scheduled · tx 0x35426005…61da05 · block 25,941,887· 2026-09-09 19:24:35 UTC
- Call to 0xac69…64e8 scheduled, executable after 1dtimelock.call_scheduled · tx 0x35426005…61da05 · block 25,941,887· 2026-09-09 19:24:35 UTC
- Scheduled call to 0xac69…64e8 executedtimelock.call_executed · tx 0xd58ca0f9…9c6686 · block 25,927,015· 2026-09-07 17:37:23 UTC
- Scheduled call to 0xac69…64e8 executedtimelock.call_executed · tx 0xd58ca0f9…9c6686 · block 25,927,015· 2026-09-07 17:37:23 UTC
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
Critical — power movedHigh — safeguards changedInfo — announced, not yet effective
Data derived from on-chain state and events only. Gliese does not custody funds and does not interpret intent — severity is assigned by how much power a change moves.