Contract control history
TimelockController on OP Mainnet — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0x07d5…7104 on OP Mainnet sits behind a 1d timelock. Gliese has recorded 2 control changes. Last checked 2026-09-11 12:41:17 UTC.
Timelock1d timelockOP Mainnet
Current control surface
snapshot 2026-09-10 11:21:12 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 |
|---|---|---|
| Call executedtimelock.call_executed | 1 | 0 |
| Call scheduledtimelock.call_scheduled | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Scheduled call to 0xb45e…9b83 executedtimelock.call_executed · tx 0x5db155f3…486bbe · block 156,765,056· 2026-09-11 12:14:49 UTC
- Call to 0xb45e…9b83 scheduled, executable after 1dtimelock.call_scheduled · tx 0xfdca9222…d12334 · block 156,720,204· 2026-09-10 11:19:45 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.