Freezes arrive in sweeps, not one at a time

Every other tracker shows you a list sorted by time, which hides the thing that matters most: whether an address was picked out on its own, or swept up with forty others. Proposals submitted within ten minutes of each other are grouped here as one batch.

Ledger
Events
17,929
Addresses
4,852
Head block
87,108,585
Latest event
23m ago
Batches
1,038
Median size
2
Largest
173
Went out alone
34%
Started (UTC)SizeComposition SpanExecutedProposals
2026-04-24 19:16 UTC
172d 22h ago
6 6 freeze 5.6 min 6 / 6 #8519–#8524
2026-04-24 12:48 UTC
173d 4h ago
13 13 freeze 14.8 min 13 / 13 #8503–#8515
2026-04-23 17:06 UTC
174d 0h ago
9 9 freeze 1.9 min 9 / 9 #8494–#8502
2026-04-22 12:33 UTC
175d 5h ago
33 10 freeze · 23 unfreeze 13.6 min 33 / 33 #8452–#8484
2026-04-20 20:51 UTC
176d 20h ago
5 5 freeze 1.9 min 5 / 5 #8432–#8436
2026-04-20 13:32 UTC
177d 4h ago
19 19 freeze 6.2 min 19 / 19 #8409–#8427
2026-04-18 21:48 UTC
178d 19h ago
5 5 freeze 3.2 min 5 / 5 #8401–#8405
2026-04-17 13:41 UTC
180d 4h ago
8 7 freeze · 1 unfreeze 10.2 min 8 / 8 #8387–#8394
2026-04-14 21:27 UTC
182d 20h ago
16 16 freeze 2.4 min 16 / 16 #8360–#8375
151–159 of 159 Newer 4 / 4 Older
Take this table with you CSV JSON
Where the ten minutes comes from. It is a grouping choice, not a fact on chain — nothing in the multisig marks where one sweep ends and the next begins. Ten minutes separates the clusters cleanly in our ledger, and every batch here lists its own span so you can judge the cut yourself.

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