Explorer ↗Watch this contract
Contract control history

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

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

1 critical, recentTimelock0s timelockBase

Current control surface

snapshot 2026-09-06 11:28:48 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 0xeb63c719…⁠addce9 · block 50,961,271
    · 2026-09-06 16:24:49 UTC
  2. Scheduled call to 0x2626…⁠e481 executed
    timelock.call_executed · tx 0xeb63c719…⁠addce9 · block 50,961,271
    · 2026-09-06 16:24:49 UTC
  3. Scheduled call to 0x7255…⁠a7d1 executed
    timelock.call_executed · tx 0xeb63c719…⁠addce9 · block 50,961,271
    · 2026-09-06 16:24:49 UTC
  4. Call to 0x2626…⁠e481 scheduled, executable after 0s
    timelock.call_scheduled · tx 0xf19bc866…⁠ce038d · block 50,961,268
    · 2026-09-06 16:24:43 UTC
  5. Call to 0x2626…⁠e481 scheduled, executable after 0s
    timelock.call_scheduled · tx 0xf19bc866…⁠ce038d · block 50,961,268
    · 2026-09-06 16:24:43 UTC
  6. Call to 0x7255…⁠a7d1 scheduled, executable after 0s
    timelock.call_scheduled · tx 0xf19bc866…⁠ce038d · block 50,961,268
    · 2026-09-06 16:24:43 UTC
  7. Scheduled call to 0x1244…⁠8e8d executed
    timelock.call_executed · tx 0xc44b00bd…⁠036d3b · block 50,940,182
    · 2026-09-06 04:41:51 UTC
  8. Timelock minimum delay changed from 1d to 0s
    timelock.min_delay_changed · tx 0xc44b00bd…⁠036d3b · block 50,940,182
    · 2026-09-06 04:41:51 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.