ProtocolTimelock on BNB Smart Chain — who can change it, and what changed

This timelock at 0x40ba…⁠ee13 on BNB Smart Chain sits behind a 30m timelock. Gliese has recorded 2 control changes and 5 deployment-time events. Last checked 2026-09-07 09:33:12 UTC.

Timelock30m timelockBNB Smart Chain

0x40ba2c0bd18c578d199be3ae692fffe74ec9ee13

Post on X Share on Telegram

Current control surface

snapshot 2026-09-07 09:31:35 UTC

Implementation: —
EIP-1967 logic contract; an upgrade changes this
Proxy admin: —
who can upgrade
Owner: —
owner()
Timelock delay: 30m
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 0x7f42…⁠c2f9 executed
timelock.call_executed · tx 0xbc97c6c5…⁠457d70 · block 120,474,787
1h ago · 2026-09-07 10:01:06 UTC
Call to 0x7f42…⁠c2f9 scheduled, executable after 30m
timelock.call_scheduled · tx 0x3d34d87e…⁠a122dd · block 120,470,741
2h ago · 2026-09-07 09:30:44 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.