Proposal #6396

freeze · executed

The multisig announced this 17.1 min before it took effect. That interval is the only warning anyone got.

Target TTutfM3tv5QA1PVYMLN71tQPehGiVdsKnx
Submitted2025-11-14 22:14 UTC
Executed2025-11-14 22:32 UTC
Interval17.1 min
Submit tx 21d5421f5a61d0e3ff5657a611ea354516524b59894f185a93d2758c881f1b99
Execute tx cab4e844a2ad45bffbd0d2aa5a9d65ee90342a9e4b3d7290e0efcf8661325f7c

Where this interval sits

Longer than 40% of the 5,967 executed freezes we hold.

Measured against executed proposals only. Counting the abandoned ones would push every percentile toward 100% and make a long wait read as “about to happen”, which is backwards.

Part of a batch. 7 other proposals went out within ten minutes either side of this one. Freezes are issued in sweeps, not one at a time — so this address was probably not singled out. See the whole sweep.

What happened on chain

  1. proposal 2025-11-14 22:14 UTC · block 77,499,029
  2. freeze 2025-11-14 22:32 UTC · block 77,499,372
  3. executed 2025-11-14 22:32 UTC · block 77,499,372

State events are matched to this proposal by target address and proximity in time. The chain carries no field binding the two, so this pairing is inference — stated plainly rather than presented as proof.

Watch this address

This page is one proposal. The bot tells you the next one, on this address, the second it is submitted.

Watch in Telegram

↑↓ move ↵ open ↵ look it up esc close Nothing you type here is stored or sent anywhere but this lookup.