Explorer ↗Watch this contract
Contract control history

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

Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay

This timelock at 0x18cb…⁠681b on Ethereum sits behind a 1d timelock. Gliese has recorded 33 control changes. Last checked 2026-09-08 01:47:20 UTC.

Timelock1d timelockEthereum

Current control surface

snapshot 2026-09-08 01:05:35 UTC
Implementation
EIP-1967 logic contract; an upgrade changes this
Proxy admin
who can upgrade
Owner
owner()
Timelock delay
1d
minimum wait between queue and execution

Recorded events

Open in the feed →
EventRealSetup
Call scheduledtimelock.call_scheduled330
Total330

Recent changes

Setup-time events hidden
  1. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  2. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  3. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  4. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  5. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  6. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  7. Call to 0x4647…⁠5b2a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  8. Call to 0x07ff…⁠a236 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x84e83a08…⁠4bfaa3 · block 25,929,259
    · 2026-09-08 01:08:11 UTC
  9. Call to 0x677a…⁠a2b5 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  10. Call to 0x1a5b…⁠100f scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  11. Call to 0xefd7…⁠db7c scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  12. Call to 0x7cb2…⁠bf02 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  13. Call to 0x4acb…⁠f6fe scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  14. Call to 0x1a5b…⁠100f scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  15. Call to 0xefd7…⁠db7c scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  16. Call to 0xcea9…⁠1396 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  17. Call to 0xcea9…⁠1396 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  18. Call to 0x4acb…⁠f6fe scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  19. Call to 0x4acb…⁠f6fe scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  20. Call to 0x1a5b…⁠100f scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  21. Call to 0x1a5b…⁠100f scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  22. Call to 0xefd7…⁠db7c scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  23. Call to 0xefd7…⁠db7c scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  24. Call to 0x677a…⁠a2b5 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  25. Call to 0x07ff…⁠a236 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  26. Call to 0xdd26…⁠be5a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  27. Call to 0xdd26…⁠be5a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  28. Call to 0xdd26…⁠be5a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  29. Call to 0xdd26…⁠be5a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  30. Call to 0x07ff…⁠a236 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  31. Call to 0x677a…⁠a2b5 scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  32. Call to 0xdd26…⁠be5a scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 UTC
  33. Call to 0x6d4a…⁠1ddb scheduled, executable after 1d
    timelock.call_scheduled · tx 0x826fd2d9…⁠4e0c3e · block 25,929,240
    · 2026-09-08 01:04:23 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.