Stablecoin freeze tracker
Tether and Circle can freeze any address on their own token contracts, and when they do, they write it to the chain. This stablecoin freeze tracker counts those events from the chain's own logs. It does not use a scraped list or a dashboard somebody updates by hand. Every row links to the transaction that did it, so you can check any number here against any node or explorer you like.
A freeze is the issuer's action, and the contract records no reason for it. Nothing here says who owns an address or why it was frozen. See why USDT gets frozen for what the flag does and does not mean, or check one address with the free USDT blacklist check.
By network
| Network | Token | Issuer | Currently frozen | Freezes lifted |
|---|---|---|---|---|
| tron | USDT | Tether | 8,199 | 980 |
| Ethereum | USDT | Tether | 2,854 | 343 |
| Ethereum | USDC | Circle | 689 | 197 |
| Base | USDC | Circle | 516 | 93 |
| Polygon | USDC | Circle | 490 | 97 |
| Avalanche | USDC | Circle | 489 | 96 |
| OP Mainnet | USDC | Circle | 487 | 93 |
| Arbitrum | USDC | Circle | 436 | 93 |
| Avalanche | USDT | Tether | 15 | 2 |
Month by month, with new sanctions listings alongside: monthly stablecoin freeze reports.
Most recent events
The issuer added these addresses to its blacklist or removed them from it. The contract gives no reason, and KYTGate does not supply one.
| Address (links to the transaction) | Token | Network | Action | When | Block |
|---|---|---|---|---|---|
| 0xb17ec513…13a141 | USDC | Ethereum | frozen | 6 Nov 2026 | 26,353,511 |
| 0x5dd0e002…f9ead6 | USDT | Ethereum | frozen | 6 Nov 2026 | 26,352,901 |
| 0x9c7f805f…f2833f | USDT | Ethereum | frozen | 6 Nov 2026 | 26,352,901 |
| 0x629e90b5…75e6f6 | USDT | Ethereum | frozen | 6 Nov 2026 | 26,352,901 |
| 0x30241bd4…5a2b50 | USDT | Ethereum | frozen | 6 Nov 2026 | 26,352,901 |
| 0xea2c0d40…55e397 | USDT | Ethereum | frozen | 6 Nov 2026 | 26,352,890 |
| TVc4K7JnR6…4BHPCB | USDT | tron | frozen | 5 Nov 2026 | 87,738,405 |
| TLkXDofLU3…d15W93 | USDT | tron | frozen | 5 Nov 2026 | 87,738,346 |
| TQgcm9vnso…hUHFei | USDT | tron | frozen | 5 Nov 2026 | 87,738,346 |
| TBckodwRD4…hP5tTE | USDT | tron | frozen | 5 Nov 2026 | 87,738,345 |
| TTaX6Dnp5a…Rt4FVB | USDT | tron | frozen | 5 Nov 2026 | 87,738,345 |
| TUd7tfHJ6x…nEmpKU | USDT | tron | frozen | 5 Nov 2026 | 87,738,297 |
| TYDwqf9KBB…dJzFLK | USDT | tron | frozen | 5 Nov 2026 | 87,722,043 |
| TS1mNfE8EN…QHmCkC | USDT | tron | frozen | 5 Nov 2026 | 87,721,920 |
| TXfVkD7ahL…shjF92 | USDT | tron | frozen | 5 Nov 2026 | 87,721,903 |
| TSgLpo6wmA…rXyCuR | USDT | tron | frozen | 4 Nov 2026 | 87,718,800 |
| TXPsUbnp8X…NjjZkM | USDT | tron | frozen | 4 Nov 2026 | 87,718,800 |
| TXi6x6cPwM…RbVBqk | USDT | tron | frozen | 4 Nov 2026 | 87,717,458 |
| TNLUsez6xu…jxea49 | USDT | tron | frozen | 4 Nov 2026 | 87,717,423 |
| TN5byy8orJ…pVndWT | USDT | tron | frozen | 4 Nov 2026 | 87,717,422 |
| TXoYeKLaVb…SkyP5y | USDT | tron | frozen | 4 Nov 2026 | 87,716,545 |
| TC2YBvEeJR…VgWRxf | USDT | tron | frozen | 4 Nov 2026 | 87,716,544 |
| TVnHfPbpPw…DN7S8T | USDT | tron | frozen | 4 Nov 2026 | 87,716,543 |
| TB1vCCzbdZ…LLSyC9 | USDT | tron | frozen | 4 Nov 2026 | 87,716,543 |
| TUiLomvFYP…GgNSd3 | USDT | tron | frozen | 4 Nov 2026 | 87,716,542 |
What has been read
A count is only meaningful alongside its coverage, so this is published too. The scan reads forward from where it started and backward through history a slice at a time.
| Network | Token | Read via | Blocks read | Complete back to | Status |
|---|---|---|---|---|---|
| Ethereum | USDT | chain node | 4,634,748 → 26,353,875 | 28 Nov 2017 | complete |
| Avalanche | USDT | chain node | 3,643,338 → 99,560,083 | 30 Aug 2021 | complete |
| Ethereum | USDC | chain node | 6,082,465 → 26,353,656 | 3 Aug 2018 | complete |
| Base | USDC | chain node | 2,797,609 → 53,772,141 | 18 Aug 2023 | complete |
| Arbitrum | USDC | chain node | 150,442,611 → 521,705,766 | 14 Nov 2023 | complete |
| Polygon | USDC | chain node | 39,320,704 → 96,826,232 | 15 Feb 2023 | complete events found below the recorded first block (49,320,704), so read from 39,320,704 |
| Avalanche | USDC | chain node | 11,907,934 → 99,560,087 | 9 Mar 2022 | complete |
| OP Mainnet | USDC | chain node | 105,235,368 → 159,173,013 | 6 Jun 2023 | complete |
| tron | USDT | explorer index | 20,972,943 → 87,757,041 | 1 Apr 2019 | complete |
Read from the issuers' own contract events on each network. Tron: TronGrid event index.
Questions people ask
What does it mean when Tether freezes an address?
Tether's USDT contract carries a blacklist its owner controls. Once an address is on it, the contract refuses to move that address's USDT: the balance still shows, but no transfer from it succeeds. Circle's USDC contracts work the same way. The contract records the freeze, not the reason. Usually it follows a law-enforcement request, but the chain does not say so, and we do not guess.
Is a frozen address the same as a sanctioned address?
No, and confusing the two is a common mistake. A freeze is an issuer's own action inside its token contract. A sanctions designation is a government publishing an address on an official list. They overlap often but neither implies the other: plenty of frozen addresses appear on no list, and most listed addresses are never frozen.
Where do these numbers come from?
From the blacklist events Tether and Circle write on-chain: AddedBlackList and RemovedBlackList on USDT, Blacklisted and UnBlacklisted on USDC. Those logs are read directly from network nodes (Tron through TronGrid's event index). Nothing is scraped from another site's page and nothing is maintained by hand, and every row links to the transaction so you can verify it yourself.
Does this cover Tron?
Yes, USDT on Tron (TRC-20), which carries the largest USDT supply and most freezes. Tron has no EVM log interface, so its AddedBlackList and RemovedBlackList events are read from TronGrid's event index of the same contract, walking history back to USDT's launch on Tron in 2019; the table below shows how far that has got. Addresses are shown in Tron's own T... form. The free per-address checker calls the contract directly and is unaffected.
My address is frozen. Can you unfreeze it?
No. Only the issuer can, and only it decides. KYTGate is compliance software for the institutions receiving deposits, not a recovery service, and anyone promising to unfreeze USDT for a fee is running a scam.
Method: KYTGate calls the official USDT and USDC contracts (listed on this page) and reads their blacklist events. Counts are distinct add events minus remove events. Bridged and wrapped variants are excluded on purpose, because they carry no issuer blacklist, so counting them would imply a coverage that does not exist. Related: addresses on the official sanctions lists, which is a different thing entirely.
Run these checks on every deposit, automatically
KYTGate screens each crypto deposit and withdrawal against the OFAC, UK and EU lists and the USDT/USDC issuer freezes, decides under your written policy, and keeps a signed record an auditor can check without us.
Start free sandboxTalk to usSee pricing
API key in two minutes, 50 screenings a month free, no card. Security · Live status · Methodology