Contract control history
TimelockController on Arbitrum One — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0x34f8…968c on Arbitrum One sits behind a 1d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-10 14:30:00 UTC.
Timelock1d timelockArbitrum One
Current control surface
snapshot 2026-09-10 13:32:58 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 scheduledtimelock.call_scheduled | 2 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Call to 0x07d5…7104 scheduled, executable after 1dtimelock.call_scheduled · tx 0xc4a1e8d6…8e6fbe · block 503,724,164· 2026-09-10 13:32:33 UTC
- Call to 0x07d5…7104 scheduled, executable after 1dtimelock.call_scheduled · tx 0xc4a1e8d6…8e6fbe · block 503,724,164· 2026-09-10 13:32:33 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.