Contract control history
TimelockController on BNB Smart Chain — who can change it, and what changed
Multisig + 24h+ timelockthis contract is a timelock with a 1d minimum delay
This timelock at 0x9551…682d on BNB Smart Chain sits behind a 1d timelock. Gliese has recorded 3 control changes. Last checked 2026-09-10 14:32:39 UTC.
Timelock1d timelockBNB Smart Chain
Current control surface
snapshot 2026-09-10 13:49:35 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 1dminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Call scheduledtimelock.call_scheduled | 3 | 0 |
| Total | 3 | 0 |
Recent changes
Setup-time events hidden- Call to 0x23e5…fa4c scheduled, executable after 1dtimelock.call_scheduled · tx 0x749d0974…fb2500 · block 121,080,839· 2026-09-10 13:48:55 UTC
- Call to 0x23e5…fa4c scheduled, executable after 1dtimelock.call_scheduled · tx 0x749d0974…fb2500 · block 121,080,839· 2026-09-10 13:48:55 UTC
- Call to 0x23e5…fa4c scheduled, executable after 1dtimelock.call_scheduled · tx 0x749d0974…fb2500 · block 121,080,839· 2026-09-10 13:48:55 UTC
Get alerted when this contract’s control changes
Free for personal wallets. Telegram, within a minute of the block.
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.