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

Timelock under 24hthis contract is a timelock with a 15m minimum delay (under 24h)

This timelock at 0x9a2d…⁠34bd on Base sits behind a 15m timelock. Gliese has recorded 2 control changes and 5 deployment-time events. Last checked 2026-09-10 19:58:42 UTC.

Timelock15m timelockBase

0x9a2d7fca01161a287823cb8c22cf148775ec34bd

Post on X Share on Telegram

Current control surface

snapshot 2026-09-10 18:53:47 UTC

Implementation: —
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Timelock delay: 15m
minimum wait between queue and execution

Recorded events

Open in the feed →

Event	Real	Setup
Role grantedaccess.role_granted	0	4
Call executedtimelock.call_executed	1	0
Call scheduledtimelock.call_scheduled	1	0
Min delay changedtimelock.min_delay_changed	0	1
Total	2	5

Recent changes

Setup-time events hidden

Scheduled call to 0x7304…⁠cd6f executed
timelock.call_executed · tx 0xaa2f426a…⁠a4b624 · block 51,139,042
3h ago · 2026-09-10 19:10:31 UTC
Call to 0x7304…⁠cd6f scheduled, executable after 15m
timelock.call_scheduled · tx 0x45b0aca1…⁠98d6c3 · block 51,138,492
3h ago · 2026-09-10 18:52:11 UTC

Full history since deployment →

Get alerted when this contract’s control changes

Free for personal wallets. Telegram, within a minute of the block.

Watch this contract Telegram bot ↗

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.