METHODOLOGY
How the freeze data is collected
Where the USDT and USDC blacklist data on this site comes from, how current it is, which wallet pages search engines may index, and how to ask for a correction.
Updated
Where the data comes from
Every freeze, unfreeze and burn on this site is an event that a stablecoin contract emitted on-chain. The index holds the blacklist events of four contracts: Tether's USDT and Circle's USDC, each on TRON and on Ethereum. Each of these contracts keeps a blacklist and refuses transfers from a blacklisted address[1][2][3].
| Token | Issuer | Network | Contract | Events |
|---|---|---|---|---|
| USDT | Tether | TRON (TRC-20) | TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t | AddedBlackList, RemovedBlackList, DestroyedBlackFunds |
| USDT | Tether | Ethereum (ERC-20) | 0xdAC17F958D2ee523a2206206994597C13D831ec7 | AddedBlackList, RemovedBlackList, DestroyedBlackFunds |
| USDC | Circle | TRON (TRC-20) | TEkxiTehnzSmSe2XqrBj4w32RUN966rdz8 | Blacklisted, UnBlacklisted |
| USDC | Circle | Ethereum (ERC-20) | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | Blacklisted, UnBlacklisted |
USDT and USDC on other networks (Solana, TON, Polygon, Avalanche and others) are not in the index, so this site has no freeze data for them. The oldest event in the index is from 28 November 2017.
How the events are collected
An on-chain scanner run by our group reads these events and stores one record per event: the contract's event name, the address, the token, the network, the time, the block number and the transaction hash. With each event it also stores the token balance it recorded for the address; for a DestroyedBlackFunds event, the amount destroyed. The site reads these records and never changes them.
Times are UTC. On Ethereum an event's time is the time of its block. On TRON it is the transaction's own timestamp, which can be a few seconds to a minute or two earlier than the block that includes it.
Every event on a wallet page links its full transaction hash to the network's explorer: Tronscan for TRON, Etherscan for Ethereum. On TRON, Tether sends blacklist changes through a multi-signature wallet contract, so Tronscan may show that contract as the recipient; the blacklist event itself is in the transaction's event log.
How often it updates
The scanner adds events as it reads new blocks. There is no fixed publication schedule, and we do not promise a fixed delay between an event on-chain and its appearance here.
On top of that, the site keeps what it has read for a short time: a wallet page up to 5 minutes, the figures on the data pages up to 1 minute, the latest-events feed 30 seconds, and the wallet sitemaps and the wallet archive (/wallets) 10 minutes.
USDT and USDC are counted apart
Tether keeps the USDT blacklist and Circle keeps the USDC blacklist. Every figure on this site is given per token: a number labelled USDT counts only USDT events, a USDC number is shown as its own figure, and nothing adds the two together. The USDC contracts have no event for destroying blacklisted funds, so burns are USDT only.
On a wallet page the status is USDT's whenever the address has a USDT event, and only USDT events decide it: a later USDC unfreeze does not clear a USDT freeze. An address with only USDC events is described as a Circle USDC record, not as USDT.
How the “as of” times work
Each status line and figure carries a date. “As of” is the time of the newest event in the whole index, not the moment you opened the page. If the scanner stops, the date stops moving, so an old figure never looks current.
A wallet page also says when it read the index (“Read …”) and when the newest indexed event happened. Rolling periods such as “last 24 hours” or “last 7 days” end at the newest event in the index.
The balance, transaction count and last activity shown live on a wallet page are read from the network when the page opens. They are not part of the freeze index, and the page says so. The USDT blacklist status is read at the time of the check too: the checker, the wallet pages and the free API ask Tether's USDT contract (getBlackListStatus, on TRON or Ethereum). The checker and the API may reuse an answer for up to 2 minutes; a wallet page may show one up to 15 minutes old, with the time it was read, while a fresh one is read. The dates, amounts and event history still come from the index.
Which wallet pages search engines may index
Every TRON and Ethereum address has a page at /wallet/<address>, and anyone can read it. Search engines may index a page only when Tether froze the address's USDT and at least one of these is true:
- Tether later unfroze it;
- Tether destroyed the frozen USDT;
- at least 10,000 USDT was on the address when it was frozen.
A few pages that search engines had already indexed before this rule stay indexable while the address's USDT freeze stands. Every other page, including smaller freezes, addresses with only USDC events and addresses with no events, carries a noindex tag, and only indexable pages are listed in the wallet sitemap. The server applies the rule from the index before it sends the page, and the sitemap uses the same rule.
Corrections and removal
If a wallet page is about your address and you think it is wrong, or you want it taken down, write to contact@usdt.lawyer or message @usdtlawyer_support_bot on Telegram. Every wallet page has a “Request a correction or removal” link that puts the address in the email's subject.
A person reads each request. If a page misstates the on-chain record, we correct it. A removal request is considered case by case, and the on-chain record itself stays public on the explorer whatever we decide. We do not promise a response time.
What a blacklist entry is not
A blacklist entry is a token-issuer action recorded on-chain; it is not proof of wrongdoing. Tether and Circle do not publish why they blacklist an address, and this site does not guess or publish any reason. No one can guarantee that frozen USDT will be released.
Sanctions list data
The only sanctions data on this site is the list of crypto addresses on the U.S. Treasury's OFAC SDN list. Our server checks OFAC's own file once a day and downloads it when it has changed; when OFAC's server sends a checksum, the download is checked against it. The wallet check and the wallet pages match addresses against it exactly (Ethereum without regard to letter case). The full list, how it is read and a CSV are on OFAC SDN crypto addresses. The list is the U.S. government's; this site copies it and adds nothing. No other sanctions list, Israel's NBCTF included, is screened.
Known limits
- The index covers the four contracts above and nothing else.
- Our index is missing USDT blacklist events: 258 on Ethereum from 15 May 2026 to 20 September 2026 and 643 on TRON from 7 August 2026 to 20 September 2026 (counted against the chain on 7 November 2026). A freeze from those periods may be missing here, and no daily or monthly report covers them.
- Because of those gaps, an address can be on Tether's blacklist with no event for it in our index. The current status is read from the USDT contract, so such an address is shown as blacklisted with a note that the event is not in our index. If the contract cannot be read at that moment, the result says the status could not be confirmed; it does not say the address is clean.
- For a TRON event our scanner records the time its transaction was signed, which can be seconds, and rarely hours, before the block that executed it. From 21 September 2026 the site uses the block time (UTC) for: the daily and monthly freeze reports; the per-day table on /reports; the monthly tables of the data pages; the latest events and the largest freezes and burns; on /analytics, the calendar, the monthly timeline and the biggest day and burn day records; and the home page's 90-day chart. These keep the scanner's times: the paired unfreezes (/unblocked-wallets), the rolling 24-hour, 7-day and 30-day figures, the by-hour and by-year charts, the year-over-year figures and the wallet pages. The events CSV keeps the scanner's time in time_utc and adds the block time in block_time_utc, empty for a TRON event whose block time we have not read (before 21 September 2026).
- An explorer shows the contract's own record. If this site and the explorer disagree, the explorer is right.
The monthly event counts by network are on the freeze analytics page.
USDT.Lawyer is a forensic and compliance team, not a law firm, and is not affiliated with Tether.
Sources
- [1] Tronscan, verified source of the USDT contract on TRON (TetherToken): “require(!isBlackListed[msg.sender]); … require(!isBlackListed[_from]);”
- [2] Etherscan, verified source of the USDT contract on Ethereum (TetherToken): “require(!isBlackListed[msg.sender]); … require(!isBlackListed[_from]);”
- [3] Circle, USDC contract source (stablecoin-evm, FiatTokenV1.sol): “whenNotPaused notBlacklisted(msg.sender) notBlacklisted(to)”
Related
More guides
- USDT frozen: what to do
First steps: confirm the freeze, keep evidence, pay no one who promises to unfreeze it.
- USDT unfreeze scam or a real freeze?
How to tell a real Tether freeze from a fee-to-unfreeze scam.
- How to unfreeze USDT
How a case to lift an unfounded freeze is built. No result is guaranteed.
- Why does Tether freeze wallets?
Law-enforcement requests, sanctions and Tether's own risk rules.
- What is the USDT blacklist?
The contract function that lets Tether freeze an address.
- Can USDT be frozen in your own wallet?
Yes, self-custody included: how the contract allows it.