Contract control history
TimelockAccepts on Ethereum — who can change it, and what changed
Timelock under 24hthis contract is a timelock with a 30s minimum delay (under 24h)
This timelock at 0x5e55…3bcf on Ethereum sits behind a 30s timelock. Gliese has recorded 2 control changes. Last checked 2026-09-10 03:25:50 UTC.
Timelock30s timelockEthereum
Current control surface
snapshot 2026-09-10 02:29:05 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 30sminimum 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 0x0b6c…68a3 executedtimelock.call_executed · tx 0xd57744bf…63c801 · block 25,944,016· 2026-09-10 02:31:35 UTC
- Call to 0x0b6c…68a3 scheduled, executable after 30stimelock.call_scheduled · tx 0x6c2319ac…48f65b · block 25,943,996· 2026-09-10 02:27:35 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.