Explorer ↗Watch this contract
Contract control history

TimelockController on Base — who can change it, and what changed

This timelock at 0x84cc…⁠879a on Base sits behind a 0s timelock. Gliese has recorded 8 control changes. Last checked 2026-09-06 11:28:46 UTC.

1 critical, recentTimelock0s timelockBase

Current control surface

snapshot 2026-09-06 11:28:46 UTC
Implementation
EIP-1967 logic contract; an upgrade changes this
Proxy admin
who can upgrade
Owner
owner()
Timelock delay
0s
minimum wait between queue and execution

Recorded events

Open in the feed →

Recent changes

Setup-time events hidden
  1. Scheduled call to 0x2626…⁠e481 executed
    timelock.call_executed · tx 0xac681239…⁠06a8ea · block 50,961,270
    · 2026-09-06 16:24:47 UTC
  2. Scheduled call to 0x2626…⁠e481 executed
    timelock.call_executed · tx 0xac681239…⁠06a8ea · block 50,961,270
    · 2026-09-06 16:24:47 UTC
  3. Scheduled call to 0x87b2…⁠f48e executed
    timelock.call_executed · tx 0xac681239…⁠06a8ea · block 50,961,270
    · 2026-09-06 16:24:47 UTC
  4. Call to 0x2626…⁠e481 scheduled, executable after 0s
    timelock.call_scheduled · tx 0x8b0254f0…⁠bc6930 · block 50,961,267
    · 2026-09-06 16:24:41 UTC
  5. Call to 0x2626…⁠e481 scheduled, executable after 0s
    timelock.call_scheduled · tx 0x8b0254f0…⁠bc6930 · block 50,961,267
    · 2026-09-06 16:24:41 UTC
  6. Call to 0x87b2…⁠f48e scheduled, executable after 0s
    timelock.call_scheduled · tx 0x8b0254f0…⁠bc6930 · block 50,961,267
    · 2026-09-06 16:24:41 UTC
  7. Scheduled call to 0x84cc…⁠879a executed
    timelock.call_executed · tx 0xdfd16e85…⁠f0cbef · block 50,940,183
    · 2026-09-06 04:41:53 UTC
  8. Timelock minimum delay changed from 1d to 0s
    timelock.min_delay_changed · tx 0xdfd16e85…⁠f0cbef · block 50,940,183
    · 2026-09-06 04:41:53 UTC
Full history since deployment →
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
Criticalpower movedHighsafeguards changedInfoannounced, 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.