The transfer posts and joins the frozen balance
If you sent USDT to an address the issuer froze before or just after your transfer, the transfer still confirms on-chain. An issuer's blacklist does not stop tokens from arriving. The token contract adds the amount to the address's balance, as it would for any other transfer, because a TRC-20 or ERC-20 contract keeps one running balance per address. Your tokens become part of what the address already held. Once the address is frozen, nobody holding the private key can move any of it, your deposit included.
Match the contract before you assume a freeze
Before you treat a stuck deposit as a freeze, confirm which token you are actually looking at. Tether issues one USDT contract per network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token labelled USDT from any other contract address is not Tether's USDT, and an issuer freeze has no bearing on it. Made-up example: a wallet shows a USDT balance from a contract address that differs from Tether's by a handful of characters in the middle. That balance was never within Tether's control to freeze, so whatever is keeping it from moving has a different cause entirely.
Once the contract checks out, look up the address itself. On Tronscan, searching the address or the transaction hash shows the sender, the recipient, the token contract, the amount and the time of the transfer. Etherscan shows the same fields for an Ethereum address. If the deposit confirms, the contract matches, and the balance has not moved despite repeated attempts to send it out, that pattern is consistent with a freeze rather than a delay or a stuck transaction.
963 wallets flagged since July, a 99.6% hit rate
We track freezes from the other direction, trying to catch each one before it lands. Tether freezes an address through a multisig wallet, which needs several signers to approve an action: one signer proposes the freeze and it executes only after the others approve. We watch those proposals instead of waiting for a published blacklist. Since 14 July 2026, our record looks like this:
- 963 wallets flagged as freeze targets ahead of the freeze itself; of the 961 with a known outcome, 957 were frozen by the issuer, a 99.6% hit rate.
- A median 10-minute gap between the flag and the freeze, and a 3.2-hour gap in nine cases out of ten.
- 873 of the flagged freezes were on TRON, with a median 6-minute gap; 80 were on Ethereum, with a median 33-minute gap.
- $418.3 million held across the flagged wallets at the moment the freeze executed.
A frozen key on one chain can expose its twin on another
Four wallets were flagged because they shared a private key with an address the issuer had just frozen on another chain, and all four were frozen afterward too. The same private key can control an address on more than one chain, so once the issuer freezes one of them, the twin address on the other chain can be next. Four is a small count next to the hundreds that followed a direct flag.
Our flags are no warning a holder can act on. A pending freeze proposal is published without the address or the exact amount until the freeze executes, so our record never gives a holder advance notice in time to move funds first. The live USDT freeze tracker lists freezes and flags that have already landed; it cannot tell you which address is next.
What to check before you write the deposit off
If a deposit you sent or received will not move, work through the steps below before deciding it is frozen for good.
Two results rule out a freeze for now. If the contract matches neither of Tether's addresses, the token is not Tether's USDT and a Tether freeze cannot be the cause. If nobody has yet tried to send the balance out, there is nothing to show whether it can move. A freeze is the likely reading only when the contract matches and a real attempt to move the balance has failed.
- Match the contract against Tether's two addresses, TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON or 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A mismatch means the question is not about an issuer freeze at all.
- Pull up the address on the matching explorer, Tronscan for TRON or Etherscan for Ethereum. Both list the sender, recipient, token contract, amount and time for every transfer in and out.
- Check for outgoing activity after the deposit landed. A balance that sits untouched through repeated attempts, paired with a contract that matches, fits a freeze rather than a delay.
- Run the address through TrustSniffer's wallet checker before you treat the funds as unrecoverable or explain the outcome to a counterparty. If the checker and the explorer point different ways, treat the balance as unresolved and do not tell anyone it is frozen yet.
Related reads: what actually happens to frozen USDT covers what the freeze record shows once a balance locks. If you received funds from a frozen address instead of sending them, see received USDT from a blacklisted address. Anyone who asks you for a fee to release a frozen balance is running the pay-to-unfreeze USDT scam.
