Contract control history
HinkalTimelockController on Arbitrum One — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 6h minimum delay (under 24h)
This timelock at 0x4c1c…622f on Arbitrum One sits behind a 6h timelock. Gliese has recorded 3 control changes. Last checked 2026-09-10 17:45:15 UTC.
1 critical, recentTimelock6h timelockArbitrum One
Current control surface
snapshot 2026-09-10 17:45:15 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 6hminimum wait between queue and execution
Recorded events
Open in the feed →Recent changes
Setup-time events hidden- Scheduled call to 0x4c1c…622f executedtimelock.call_executed · tx 0x166c79f0…aadf0b · block 503,776,516· 2026-09-10 17:12:33 UTC
- Timelock minimum delay changed from 3m to 6htimelock.min_delay_changed · tx 0x166c79f0…aadf0b · block 503,776,516· 2026-09-10 17:12:33 UTC
- Call to 0x4c1c…622f scheduled, executable after 3mtimelock.call_scheduled · tx 0x82d4958e…b48d37 · block 503,774,955· 2026-09-10 17:06: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.