Contract control history
Timelock on BNB Smart Chain — who can change it, and what changed
This timelock at 0xa1f4…8fe4 on BNB Smart Chain sits behind a 6h 1m timelock. Gliese has recorded 2 control changes. Last checked 2026-09-07 05:27:39 UTC.
Timelock6h 1m timelockBNB Smart Chain
Current control surface
snapshot 2026-09-07 05:27:39 UTC- Implementation
- —EIP-1967 logic contract; an upgrade changes this
- Proxy admin
- —who can upgrade
- Owner
- —owner()
- Timelock delay
- 6h 1mminimum wait between queue and execution
Recorded events
Open in the feed →| Event | Real | Setup |
|---|---|---|
| Execute transactiontimelock.execute_transaction | 1 | 0 |
| Queue transactiontimelock.queue_transaction | 1 | 0 |
| Total | 2 | 0 |
Recent changes
Setup-time events hidden- Transaction burnCake() to 0xa5f8…7652 queuedtimelock.queue_transaction · tx 0x6fe04315…2240ab · block 120,438,260· 2026-09-07 05:27:02 UTC
- Queued transaction burnCake() to 0xa5f8…7652 executedtimelock.execute_transaction · tx 0x6fe04315…2240ab · block 120,438,260· 2026-09-07 05:27:02 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.