Contract control history
TimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 10m minimum delay (under 24h)
This timelock at 0xd216…7e5e on Ethereum sits behind a 10m timelock. Gliese has recorded 3 control changes. Last checked 2026-09-11 15:56:19 UTC.
Timelock10m timelockEthereum
Current control surface
snapshot 2026-09-11 15:15:37 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 10mminimum 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 0xd216…7e5e scheduled, executable after 10mtimelock.call_scheduled · tx 0xb46c6541…e43644 · block 25,954,990· 2026-09-11 15:14:35 UTC
- Call to 0xd216…7e5e scheduled, executable after 10mtimelock.call_scheduled · tx 0xb46c6541…e43644 · block 25,954,990· 2026-09-11 15:14:35 UTC
- Call to 0xd216…7e5e scheduled, executable after 10mtimelock.call_scheduled · tx 0xb46c6541…e43644 · block 25,954,990· 2026-09-11 15:14: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.