Proposal #6709

freeze · executed

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

Target TB6agEwmYP71w9Tu5Wf8Gjtvraqz2NM2JA
Submitted2025-12-24 22:02 UTC
Executed2025-12-24 22:29 UTC
Interval27.8 min
Submit tx 7970ae0f2ac5bec117eba2981f4be702b2e390fd211e5d9a9e4f6014faa44f13
Execute tx c36778462ca87c705a42f041627b1d13667f01c3a92ca171ee16975af16eae07

Where this interval sits

Longer than 47% 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-12-24 22:02 UTC · block 78,650,330
  2. freeze 2025-12-24 22:29 UTC · block 78,650,886
  3. executed 2025-12-24 22:29 UTC · block 78,650,886

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.