Contract control history
TimelockController on Arbitrum One — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 2d minimum delay
This timelock at 0xab9e…5611 on Arbitrum One sits behind a 2d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-11 15:58:42 UTC.
Timelock2d timelockArbitrum One
Current control surface
snapshot 2026-09-11 15:21:52 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 | 1 | 0 |
| Call scheduledtimelock.call_scheduled | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Call to 0xf6d5…7d6c scheduled, executable after 2dtimelock.call_scheduled · tx 0x624d3813…f70920 · block 504,091,086· 2026-09-11 15:21:08 UTC
- Scheduled call to 0xf6d5…7d6c executedtimelock.call_executed · tx 0x76943634…f74733 · block 504,086,324· 2026-09-11 15:01:21 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.