Contract control history
Timelock 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 0x3fb4…f88a on Arbitrum One sits behind a 1d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 19:58:35 UTC.
Timelock1d timelockArbitrum One
Current control surface
snapshot 2026-09-07 19:04:09 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 |
|---|---|---|
| Queue transactiontimelock.queue_transaction | 2 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Transaction deployAndUpgradeTo() to 0xd10b…715e queuedtimelock.queue_transaction · tx 0x233345c5…383fb5 · block 502,772,238· 2026-09-07 19:03:00 UTC
- Transaction deployAndUpgradeTo() to 0xd10b…715e queuedtimelock.queue_transaction · tx 0x233345c5…383fb5 · block 502,772,238· 2026-09-07 19:03:00 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.