Contract control history
TimelockController on Base — who can change it, and what changed
This timelock at 0x93e4…c872 on Base sits behind a 2d timelock. Gliese has recorded 4 control changes. Last checked 2026-09-06 11:01:34 UTC.
Timelock2d timelockBase
Current control surface
snapshot 2026-09-06 11:01:34 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 executedtimelock.call_executed | 2 | 0 |
| Call scheduledtimelock.call_scheduled | 2 | 0 |
| Total | 4 | 0 |
Recent changes
Setup-time events hidden- Call to 0xae79…a548 scheduled, executable after 2dtimelock.call_scheduled · tx 0x3c71939c…70b822 · block 50,951,551· 2026-09-06 11:00:49 UTC
- Scheduled call to 0xae79…a548 executedtimelock.call_executed · tx 0x37cfcb43…9ad055 · block 50,950,953· 2026-09-06 10:40:53 UTC
- Call to 0xae79…a548 scheduled, executable after 2dtimelock.call_scheduled · tx 0xc18c0460…d911dc · block 50,935,371· 2026-09-06 02:01:29 UTC
- Scheduled call to 0xae79…a548 executedtimelock.call_executed · tx 0xb2466ce0…a818b8 · block 50,934,765· 2026-09-06 01:41:17 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.