Every stablecoin freeze and seizure on record — with evidence.

Free · No account · Unlimited checks

What we cover

56 tokens across 79 contracts on 17 blockchains — 43,107 recorded events since 2018, as of 26 August 2026. Free to read, no account.

Data as of

What we have recorded on each blockchain, 2018 to 26 August 2026
Blockchain Events Wallets Seizures
Ethereum 17,554 5,780 1,207
Tron 11,915 8,329 1,127
Base 2,339 628
Gnosis 2,126 2,036
Polygon 1,761 1,109 17
Arbitrum 1,717 587 5
Avalanche 1,618 534 9
BNB Chain 1,011 867
Optimism 658 514
HyperEVM 639 524 1
Celo 610 514 1
Sonic 443 420
Mantle 368 365
Robinhood 254 183
Solana 84 76 3
Stellar 6 3
Adi 4 2

A dash means no seizure has been recorded on that blockchain, as of 26 August 2026.

By token

56 tokens have at least one recorded event, across 79 contracts. The full table — one row per token and the company that controls it — is on the tokens page.

How we compare

What each tracker covered when we read its site, next to our own generated counts.

Coverage by tracker
Tracker Tokens Chains History Amounts API
Eagle Virtual (this site) 56 17 Since 2018, every event dated Balances read from the chain at a named block Free API and MCP server
blocklist.fyi 3 (USDT, USDC, USD1) "40+" (its own claim) Free, capped at 100 calls a day
usdtbanlist.com 3 (USDT, USDC, A7A5) 2 (Tron, Ethereum) Paid, plus a Telegram bot
Pharos FreezeWatch About 10 Multi-chain Open source, non-commercial
Block explorers Own chain only None — the current flag only

Competitor figures read from each site on 27 August 2026; ours are generated from our records and dated above. A dash means we make no claim for that cell.

How we count

Freeze trackers disagree with each other because they count different things. This is our method, in full, so our numbers can be checked.

An event is an on-chain write

Every event in our record is a write the issuer's contract made on the blockchain — a freeze, a release, a blacklisting, or a seizure — cited by its transaction hash and block number. We record what happened. We do not predict, and we do not score anyone.

Native and bridged tokens are counted separately

The token a company issues and the copy a bridge wraps onto another chain are different contracts under different control. We count them separately and label the bridged one — it shows with a BRIDGED tag, attributed to the bridge operator — so a bridge's actions are never counted as the issuer's.

What a measured amount is

Where an amount was measured, it is the wallet's balance read from the chain at the block the event names: the event's own block for a freeze, and the block before it for a seizure, because a seizure destroys the balance in its own block. Each measured amount is published with which reading it is. A USD figure appears only where certified pricing exists for that token at that block; otherwise we show a dash — never $0.00, and never today's price on an old event.

Freshness is part of the answer

Every answer names the block and the time it was checked. If our reading of a blockchain falls behind, every answer that touches that blockchain says so, for that chain and for each token on it, until the reading has caught up.

Corrections are public

When a record was wrong, we correct it and say so. The policy, and how to report a mistake, are on the corrections page.

Read the record

Questions people ask

How many blockchains do you check?

17, as of 26 August 2026: Ethereum, Tron, Base, Gnosis, Polygon, Arbitrum, Avalanche, BNB Chain, Optimism, HyperEVM, Celo, Sonic, Mantle, Robinhood, Solana, Stellar, Adi.

Do you cover my token?

The tokens page lists every token with at least one recorded event — 56 of them, as of 26 August 2026 — with the company that controls each one. If a token is not listed, we have no recorded event for it on the blockchains we check, as of that date.

How do you count differently from other trackers?

Counts disagree between trackers because methods differ. Ours is published in full on this page: an event is a write the issuer’s contract made on the blockchain, cited by its transaction, so each of our numbers can be checked against the chain.

How far back does the record go?

The first event in the record is from 2018. Every event since then carries its date, its transaction hash and its block number.