Contract control history
TimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 5m minimum delay (under 24h)
This timelock at 0xd48e…9a38 on Ethereum sits behind a 5m timelock. Gliese has recorded 9 control changes. Last checked 2026-09-08 10:11:51 UTC.
Timelock5m timelockEthereum
Current control surface
snapshot 2026-09-08 09:58:12 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 5mminimum wait between queue and execution
Recorded events
Open in the feed →Recent changes
Setup-time events hidden- Scheduled call to 0xd48e…9a38 executedtimelock.call_executed · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- EXECUTOR_ROLE revoked from the zero addressaccess.role_revoked · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- Scheduled call to 0xd48e…9a38 executedtimelock.call_executed · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- EXECUTOR_ROLE granted to 0x16ce…a3aeaccess.role_granted · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- Scheduled call to 0xd48e…9a38 executedtimelock.call_executed · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- EXECUTOR_ROLE granted to 0xe61a…530daccess.role_granted · tx 0x12be8f9f…8b647a · block 25,932,005· 2026-09-08 10:19:23 UTC
- Call to 0xd48e…9a38 scheduled, executable after 5mtimelock.call_scheduled · tx 0x05444347…f614ba · block 25,931,893· 2026-09-08 09:56:35 UTC
- Call to 0xd48e…9a38 scheduled, executable after 5mtimelock.call_scheduled · tx 0x05444347…f614ba · block 25,931,893· 2026-09-08 09:56:35 UTC
- Call to 0xd48e…9a38 scheduled, executable after 5mtimelock.call_scheduled · tx 0x05444347…f614ba · block 25,931,893· 2026-09-08 09:56: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.