Contract control history
TimelockController on Ethereum — who can change it, and what changed
This timelock at 0x14f5…3407 on Ethereum sits behind a 0s timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 09:23:24 UTC.
Timelock0s timelockEthereum
Current control surface
snapshot 2026-09-07 09:10:27 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 0sminimum 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 0xff8b…f4f6 executedtimelock.call_executed · tx 0x10d83afa…9ff48e · block 25,924,492· 2026-09-07 09:09:59 UTC
- Call to 0xff8b…f4f6 scheduled, executable after 0stimelock.call_scheduled · tx 0x0356a2d4…e37d77 · block 25,924,488· 2026-09-07 09:09:11 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.