Contract control history
TimelockController on Ethereum — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 3d minimum delay
This timelock at 0x3518…4707 on Ethereum sits behind a 3d timelock. Gliese has recorded 4 control changes. Last checked 2026-09-07 20:32:32 UTC.
Timelock3d timelockEthereum
Current control surface
snapshot 2026-09-07 20:01:48 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 3dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call scheduledtimelock.call_scheduled | 4 | 0 |
| Total | 4 | 0 |
Recent changes
Setup-time events hidden- Call to 0xdac1…1ec7 scheduled, executable after 3dtimelock.call_scheduled · tx 0x27751e11…d5b859 · block 25,927,727· 2026-09-07 20:00:35 UTC
- Call to 0xa0b8…eb48 scheduled, executable after 3dtimelock.call_scheduled · tx 0x27751e11…d5b859 · block 25,927,727· 2026-09-07 20:00:35 UTC
- Call to 0xba49…ebaa scheduled, executable after 3dtimelock.call_scheduled · tx 0x27751e11…d5b859 · block 25,927,727· 2026-09-07 20:00:35 UTC
- Call to 0xba49…ebaa scheduled, executable after 3dtimelock.call_scheduled · tx 0x27751e11…d5b859 · block 25,927,727· 2026-09-07 20:00:35 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.