Live · 2067 days of chain history

USDT freeze data, in public

Everything below is derived from our own event ledger — 5,964 proposals, refreshed every 10 seconds. The contracts are listed on How it works; every figure is reproducible from them, and the rows behind it are in the explorer.

24h 7d 30d 90d 6M 1Y All

Counts follow the range filter above
Freezes	1,090	12.1 per day
Unfreezes	34	3% of freezes, same window
Destroys	127	39,776,145.05 USDT
Proposals	1,258	5 awaiting execution right now

All-time, independent of the filter — a 24-hour slice of these would be noise rather than a number
Median window	36.0 min	5,894 paired proposals
Execution rate	98.74%	of proposals that were submitted
Ledger	17,850	events, to block 87,105,640

Freezing over time

Events per calendar month. Freezes form the base of each bar; unfreezes and destroys stack above them, to the same scale.

Sep

Oct

Nov

Dec

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

freeze unfreeze destroy 2025-09 – 2026-10

How long the window is

Share of proposals whose delay fell in each band.

< 1m 2.5%

1m–5m 27.7%

5m–30m 18.1%

30m–2h 22.7%

2h–6h 18.1%

6h–1d 9.7%

> 1d 1.2%

How much reaction time

Share of proposals that gave you at least this long.

≥ 30s 99.5%

≥ 1m 97.5%

≥ 5m 69.7%

≥ 15m 61.1%

≥ 1h 41.8%

So how fast do you need to be?

Everything above is a distribution; this is the question behind it. Pick how long it would realistically take you to react, and this reads off what share of executed freezes gave you at least that much warning.

If you react within

15 min

You are ahead of

—

Out of

5,894 executed freezes

Reaction time

within 53 sec

98.9%

within 4.6 min

70.1%

within 24.3 min

55.6%

within 2.1 hr

27.9%

within 11.2 hr

5.7%

The floor this can never cross. 2 of 5,894 freezes (0.03%) executed in the same block they were proposed in. No reaction time reaches those, and no alerting service can create a window that isn't there. The curve is measured, not modelled — every point is a count of real proposals, and proposals that never executed are excluded because they have no window to measure.

Freezing keeps office hours

When proposals are submitted, in UTC. Risk is not spread evenly across the day or the week — which is actionable if you settle trades on a schedule.

By hour (UTC)

00

06

12

18

By weekday (UTC)

Mon 889

Tue 1,087

Wed 1,101

Thu 1,648

Fri 838

Sat 238

Sun 168

Freezes arrive in sweeps

Proposals separated by more than ten minutes count as separate batches. The shape matters: being caught in a sweep of 173 means something different from being singled out.

Batches	1,036
Median batch	2
Largest batch	173
Issued alone	34%

Open every sweep — each one as a list of who went out together.

Is the warning shrinking?

Median window per month. If this line trends down, this product's value trends down with it — better we publish it than you discover it.

Nov

Dec

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Tallest bar = 2.7 hr.

For the addresses that were released

Time between the freeze and the release, for the 681 addresses that were released at all.

This is a survivor sample. The denominator is addresses that were released — not addresses that were frozen. It answers “how long did the released ones wait”, and it does not answer “how long will mine take”. We don't guarantee any outcome and cannot influence one.

0s–1h 0.4%

1h–1d 1.5%

1d–7d 4.3%

7d–30d 15.7%

30d–∞ 78.1%

Median	44.0 d
90th percentile	50.0 d
Sample	681 addresses
Frozen, all time	4,482 events

Proposals awaiting execution

5 awaiting execution — 5 freeze, 0 unfreeze or destroy.

Address	Action	Submitted	Proposal
TT8cuuJQa1j8qt6WUrSTjZGqMhjf5X9MsN	freeze	5m ago	#11411
TLWQyZAJ2gUV1hhH6G21X7ymfkgRTy8vwU	freeze	5m ago	#11410
TYFRs2GdfQT4wGrwQTZuRwELvCauYpprtr	freeze	5m ago	#11409
TXxCNfwnCHTHR5fCBVAus9J7LqruPvsorC	freeze	5m ago	#11408
TLnQpyNYTubQkhxDJLzHDGduxnsTgiuskQ	freeze	6m ago	#11407

70 more have sat unexecuted past 7 days. Measured behaviour says abandoned — excluded, never alerted.

Biggest destroys

Destruction is a step past freezing. Most frozen addresses never reach it.

USDT	Address	When
15,000,000.00	TFzQYnrjjKrTWC…	375d 23h ago
10,000,001.16	THRttTJKKLmAPd…	321d 17h ago
10,000,001.00	TTrq4BEVoF3uWV…	321d 17h ago
10,000,000.38	TKk4KBH5zYFzyH…	235d 20h ago
8,000,200.09	TQ9fFX3BW9F4Js…	375d 23h ago
7,241,603.53	TXwaQMRbLD4tt1…	239d 22h ago
7,100,000.00	TWvuuXuHCgRPrs…	321d 17h ago
6,499,970.70	TM2xwqYoZwPyYz…	277d 2h ago

Frozen more than once

A release is not a clean slate. These addresses went through the cycle more than once.

Address	Freezes	Unfreezes	Last
TFB5wGzo8T3oWW…	3	1	19d 2h ago
TV1ErMvnSFdGdh…	3	1	19d 2h ago
TZ9ZSexQTiydf7…	2	1	20d 0h ago
TBZRekL7YiwHfF…	2	1	22d 14h ago
TLUcMY1TXBPBRA…	2	1	110d 22h ago
TCDH9QwK3Bh3WJ…	2	1	110d 22h ago
TCbktVvCv4qCMF…	2	1	110d 22h ago
TWoHZYFBT1aQx8…	2	1	112d 19h ago

Method. Proposals pair with executions by multisig transaction id. “Awaiting execution” means no Execution event and submitted within 7 days; anything older behaves as abandoned and is counted separately. We publish destroyed value but not “total value frozen” — that would need a historical balance snapshot per address, which we don't have, and estimating it would make the number worse than absent. Ledger covers 17,850 events up to block 87,105,640.