A deposit that's really there, and a login that isn't
USDT shows up in a wallet, then later the balance won't move, or an exchange app says the account is under review. Both get described as "frozen," and they are not the same thing. One is enforced by code that Tether controls. The other is a decision made inside an exchange's own systems, with the tokens themselves untouched the whole time.
Genuine USDT exists as one contract per network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token using the USDT name from any other contract is not Tether's token, no matter what the balance display claims. When Tether blacklists an address on one of these contracts, that is the issuer acting directly on the token; an exchange freezing your account access is a separate system entirely, and it leaves no mark on either contract.
A token's balance is one number tied to an address, and a transfer adds to whatever that address already holds. Nothing sits in a quarantined pile waiting on a decision, so USDT sent to a blacklisted address joins its balance and is frozen along with the rest. An exchange hold works differently: your tokens stay in a wallet the exchange controls, and the block applies to your login and withdrawal rights.
What a Tether blacklist looks like on Tronscan and Etherscan
Tronscan and Etherscan show what happened at the contract, and an exchange's internal decisions never appear there. Search the address and you see every transfer in and out: sender, recipient, the token contract, the amount and the time. If the address keeps receiving USDT but its attempts to send it out show as failed, Tether has blacklisted it at the contract level, which is what an issuer freeze looks like on-chain. An address with no outgoing transfers at all proves less, because the owner may simply not have tried to send anything. If transfers run normally in both directions right up to a withdrawal that was blocked somewhere else, the freeze sits in the exchange's own records and the explorer won't explain it.
1,073 of 1,080 flagged wallets, and four frozen by association
As of 2026-10-11, TrustSniffer's live tracker has flagged 1,080 wallets as likely issuer freeze targets since 2026-07-14, built from Tether's own multisig freeze proposals. Of the 1,078 flagged wallets where the outcome is now known, 1,073 were frozen, a 99.5% hit rate. Between them, those wallets held $444.5 million at the moment the freeze landed.
- TRON: 976 of the flagged freezes went through, with a median gap of 5 minutes between the flag and the freeze.
- Ethereum: 93 freezes landed, with a median gap of 33 minutes.
- The head start is the time between our flag and the freeze itself. Across both networks the median was 6 minutes, and the slowest 10% of cases took up to 3.2 hours.
- Four wallets were frozen by association. A private key is the secret that signs transfers, and one key can control an address on TRON and another on Ethereum. Each of these four held the same private key as an address the issuer had just frozen on the other network, and the issuer froze the twin as well.
- The tracker has one built-in gap. Tether publishes freeze proposals before they execute, but the address and the exact amount only become visible once the freeze is done. Our flag confirms which wallet was targeted; it can't warn the holder in time to move funds out first.
Four checks on Tronscan or Etherscan before you decide
Work through these in order:
- Match the contract. Confirm the token you're checking is the real USDT contract, TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON or 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A lookalike token on a different contract isn't frozen by Tether at all, because it isn't Tether's token.
- Read the transfer history. Each row on the explorer shows the sender, the recipient, the amount and the time. Look for outgoing transfers from the address and check whether they succeeded or failed.
- Decide what the pattern means. Outgoing transfers that fail point to a contract-level freeze, which is final and which an exchange support ticket cannot undo. Normal transfers both ways until a withdrawal was blocked elsewhere mean the hold sits with whoever controls that wallet or account. Incoming transfers with no outgoing ones at all don't settle it on their own, so go to the next step.
- If the result is unclear, for example a mix of successful and failed outgoing transfers, check the address with our wallet checker and compare it against the live USDT freeze tracker, then ask the exchange or counterparty directly which side is holding the funds.
Where to go next
If the hold is on an exchange account, exchange froze account after a USDT deposit covers the explorer fields support will ask you for. For a Binance deposit in particular, frozen USDT on Binance shows where to find the sender address in the deposit history. If Tether did blacklist the address, what actually happens to frozen USDT explains what the freeze record covers after that point and what it leaves open.


