One hold happens on chain, the other never does

USDT frozen almost always means one of two separate things, and they are not interchangeable. Either Tether blacklisted the wallet address inside the token contract itself, a change anyone can verify by looking the address up, or a platform holding your funds decided internally to block a withdrawal, which leaves no trace on the blockchain at all. Mixing the two up leads to the wrong next step: appealing to an exchange does nothing for a contract-level blacklist, and staring at a block explorer tells you nothing about an internal account hold.

TrustSniffer has flagged 924 wallets since 2026-07-14 as likely freeze targets by watching Tether's multisig proposals before they execute (see the live USDT freeze tracker). Of the 921 flagged wallets with a known outcome, 918 were frozen by the issuer, a 99.7% hit rate. That accuracy is only possible because the signal comes from the same place the freeze itself comes from, the multisig proposal queue, not a guess about which exchange might be involved.

TRON freezes in 7 minutes, Ethereum takes 33

The two networks carrying most USDT supply do not move at the same pace once a freeze proposal appears. On TRON, 834 freezes were flagged in advance from Tether's multisig proposals, with a median head start of 7 minutes before the issuer executed the freeze. On Ethereum, 80 freezes were flagged the same way, with a median head start of 33 minutes, close to five times longer.

Across both chains combined, the median head start is 10 minutes and the 90th percentile is 3.2 hours. The wallets flagged this way held $413.3 million between them at the moment of the freeze, money sitting in addresses the proposal queue had already named as a target before it was acted on.

When a frozen key freezes its twin on another chain

Freezes are not always isolated events. 4 wallets were flagged because they held the cross-chain twin of a key the issuer had already frozen on a different network, and all four were then frozen themselves. The same private key can control an address on more than one chain, so a blacklist against one side of that key is a strong hint the other side is next.

Telling an issuer blacklist from an exchange hold

The chain itself will tell you which situation you are in, if you know where to look. A block explorer or the wallet checker will show a blacklist flag directly on the address if Tether froze it at the contract level. If the address looks completely normal on-chain, balance intact, no flag, and your withdrawal is still blocked, the hold is sitting inside a platform's own ledger, not on the blockchain.

If the on-chain record looks clean, check the platform holding your funds with the website checker before assuming the money is gone. A hold inside an account is a different problem than a contract-level freeze, and it usually has a different, faster resolution.

  • A blacklisted address shows the flag on-chain, and no appeal to an exchange will undo it, because the contract itself is enforcing the block.
  • A clean address with a blocked withdrawal means the hold is inside the platform's account system, and the chain has no record of why.

What the freeze tracker sees, and what it can't

TrustSniffer builds this picture by watching Tether's multisig proposals as they are submitted, before the freeze executes on either chain. That is what makes a lead time of minutes possible instead of finding out after the fact.

Pending freeze proposals are published without their address or exact amount until the freeze actually executes, so the record never warns a specific holder in time to move funds. It confirms a freeze is coming and documents it once it lands, but it cannot name the target early enough to act on.