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

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

This timelock at 0x65c6…⁠97c0 on BNB Smart Chain sits behind a 6h timelock. Gliese has recorded 3 control changes. Last checked 2026-09-10 17:48:47 UTC.

1 critical, recentTimelock6h timelockBNB Smart Chain

0x65c649917df3359fbaddf262adb8aa8e486897c0

Post on X Share on Telegram

Current control surface

snapshot 2026-09-10 17:48:47 UTC

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

Recorded events

Open in the feed →

Event	Real	Setup
Call executedtimelock.call_executed	1	0
Call scheduledtimelock.call_scheduled	1	0
Min delay changedtimelock.min_delay_changed	1	0
Total	3	0

Recent changes

Setup-time events hidden

Scheduled call to 0x65c6…⁠97c0 executed
timelock.call_executed · tx 0xf556f4a8…⁠ca1de0 · block 121,109,268
1h ago · 2026-09-10 17:22:10 UTC
Timelock minimum delay changed from 3m to 6h
timelock.min_delay_changed · tx 0xf556f4a8…⁠ca1de0 · block 121,109,268
1h ago · 2026-09-10 17:22:10 UTC
Call to 0x65c6…⁠97c0 scheduled, executable after 3m
timelock.call_scheduled · tx 0x40fa7fa4…⁠6180e9 · block 121,108,337
2h ago · 2026-09-10 17:15: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.