Three checks: the contract, the explorer, the tracker
No single flag tells you whether a suspect USDT balance is safe to hold. Three checks together show what you hold: the contract behind the token, the transaction trail on a public explorer, and whether any wallet in that trail is already on TrustSniffer's live record of issuer freezes.
- Match the contract first. Genuine USDT runs from one contract per network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token calling itself USDT from any other contract address is not Tether's USDT, and the real contract's status tells you nothing about it.
- Read the transfer history. Search a TRON address or transaction hash on Tronscan to see every transfer that address has made. Each transfer is listed with its sender, recipient, contract, amount and time. Etherscan shows the same fields for Ethereum. Work back through recent transfers and write down each address yours has sent to or received from. The current balance alone does not show who the address has dealt with.
- Paste each counterparty into the live USDT freeze tracker. It lists the wallets we flagged from Tether's multisig proposals and whether they were frozen. Then run the address itself through the wallet checker to see the risk signals we hold on it. If a counterparty is listed on the tracker, treat that as the result that counts, even when your own address comes back clean: your address has dealt with a wallet Tether moved to freeze.
873 TRON freezes flagged before Tether's multisig fired
Tether freezes a wallet through a multisig proposal, a request that several of its signers must approve before the freeze runs. We read each proposal before it executes. Since 2026-07-14 that has let us flag 963 wallets as freeze targets before Tether acted. For 961 of them we know the outcome, and 957 of those were frozen, a 99.6% hit rate.
TRON is where most of the activity is: 873 of those freezes were flagged there, with a median lead of 6 minutes between our flag and the freeze. On Ethereum we flagged 80, with a slower median lead of 33 minutes, which reflects how quickly each chain's proposal process moves. Across both networks the median head start is 10 minutes, and it stretches to 3.2 hours at the 90th percentile. When the freezes landed, the wallets we flagged held $418.3 million between them.
Four wallets frozen as a frozen key's cross-chain twin
A smaller pattern sits on top of the freezes themselves: 4 wallets were frozen after we flagged them as the cross-chain twin of a key the issuer had already frozen on another network, the same address format holding a presence on both TRON and Ethereum. That signal only fires once the first side is already frozen, and pending proposals are published without their address or exact amount until the freeze executes, so the record cannot warn a holder of a still-pending wallet in time to move funds before it locks.
Why a clear check today does not mean a clean history
Passing all three checks describes the address on the day you looked. An ERC-20 or TRC-20 token keeps one balance per address, and each transfer adds straight into it. If the wallet that paid you is frozen next week, the funds it sent are already part of your balance and cannot be told apart from the rest. You will only see that link if you check the counterparties again after the source is flagged.
Made-up example: two TRON addresses end in ...8pQr and ...8pQs, one character apart. A clean check on one tells you nothing about the other. Compare the complete address string with the one you actually sent to or received from. A familiar-looking ending proves nothing.
How the tracker is built from Tether's live multisig proposals
We build the freeze tracker by reading Tether's multisig proposals as they are submitted. It does not match addresses against a published sanctions list. It shows freezes Tether has already set in motion and says nothing about why Tether chose a given address.
If the contract matches, the explorer shows no link to a flagged counterparty and the tracker comes back clear, treat the address as unflagged at the time you checked, and recheck before relying on an old result. If a transfer traces back to a wallet already listed there, or the trail is too long to follow by hand, run it through the wallet checker. If that result is unclear, leave the funds where they are and do not send them on to anyone until you can trace where they came from.
Related reads: can USDT be frozen explains the on-chain mechanism these checks look for, received USDT from a blacklisted address covers what to do when a counterparty does turn up on the tracker, and checking USDT before a P2P trade applies the same contract and explorer reads to a trade you have not settled yet.


