Proposal #5739

freeze · executed

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

Target TPukKcTqUNLGV6GTgmoLLQSeoJwSo2x9Ak
Submitted2025-09-22 10:47 UTC
Executed2025-09-22 11:14 UTC
Interval27.4 min
Submit tx e02e246ff84379d09f4dd7380e2aaadb7cc43156e8af9927b3f37d71f891911b
Execute tx 44ecc6cffa518bbf894804fa502e7eb32f05e3050bfe04c7bbad8db1deec7fb9

Where this interval sits

Longer than 47% of the 5,914 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. 122 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-09-22 10:47 UTC · block 75,959,321
  2. freeze 2025-09-22 11:14 UTC · block 75,959,868
  3. executed 2025-09-22 11:14 UTC · block 75,959,868

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.