Contract control history
TimelockController on Arbitrum One — who can change it, and what changed
This timelock at 0x29f8…3403 on Arbitrum One sits behind a 1d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 02:06:29 UTC.
Timelock1d timelockArbitrum One
Current control surface
snapshot 2026-09-07 02:06:29 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1dminimum 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 0x7fab…8b01 executedtimelock.call_executed · tx 0xf64b91d4…8ee9cd · block 502,532,344· 2026-09-07 02:10:02 UTC
- Call to 0x7fab…8b01 scheduled, executable after 1dtimelock.call_scheduled · tx 0xd5927c03…bebe8d · block 502,531,197· 2026-09-07 02:05:02 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.