Contract control history
HinkalTimelockController on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 6h minimum delay (under 24h)
This timelock at 0xf043…b7d0 on Ethereum sits behind a 6h timelock. Gliese has recorded 3 control changes. Last checked 2026-09-10 17:43:48 UTC.
1 critical, recentTimelock6h timelockEthereum
Current control surface
snapshot 2026-09-10 17:43:48 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 0xf043…b7d0 executedtimelock.call_executed · tx 0x406f2509…4f5681 · block 25,948,466· 2026-09-10 17:24:47 UTC
- Timelock minimum delay changed from 3m to 6htimelock.min_delay_changed · tx 0x406f2509…4f5681 · block 25,948,466· 2026-09-10 17:24:47 UTC
- Call to 0xf043…b7d0 scheduled, executable after 3mtimelock.call_scheduled · tx 0x00aa5ab8…bcf31a · block 25,948,437· 2026-09-10 17:18:59 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.