Contract control history
TimelockController on Ethereum — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 2d minimum delay
This timelock at 0x9eba…2f91 on Ethereum sits behind a 2d timelock. Gliese has recorded 3 control changes. Last checked 2026-09-10 14:29:35 UTC.
Timelock2d timelockEthereum
Current control surface
snapshot 2026-09-10 14:00:45 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 2dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call scheduledtimelock.call_scheduled | 3 | 0 |
| Total | 3 | 0 |
Recent changes
Setup-time events hidden- Call to 0x07ac…d085 scheduled, executable after 2dtimelock.call_scheduled · tx 0x5a6335b8…039a93 · block 25,947,441· 2026-09-10 13:59:11 UTC
- Call to 0xa151…a332 scheduled, executable after 2dtimelock.call_scheduled · tx 0x5a6335b8…039a93 · block 25,947,441· 2026-09-10 13:59:11 UTC
- Call to 0x0acd…58ac scheduled, executable after 2dtimelock.call_scheduled · tx 0x5a6335b8…039a93 · block 25,947,441· 2026-09-10 13:59:11 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.