Contract control history
TimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 1h minimum delay (under 24h)
This timelock at 0x4d02…0336 on Ethereum sits behind a 1h timelock. Gliese has recorded 2 control changes. Last checked 2026-09-09 15:24:32 UTC.
Timelock1h timelockEthereum
Current control surface
snapshot 2026-09-09 14:52:39 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1hminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call executedtimelock.call_executed | 1 | 0 |
| Call scheduledtimelock.call_scheduled | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0xe5a1…3fb3 executedtimelock.call_executed · tx 0xdc0c4e62…d7ac96 · block 25,941,066· 2026-09-09 16:39:35 UTC
- Call to 0xe5a1…3fb3 scheduled, executable after 1htimelock.call_scheduled · tx 0xe473ecf0…3bd8c6 · block 25,940,529· 2026-09-09 14:51:59 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.