The payment that freezes you came from someone else's history

You released the fiat, and not long after, the P2P platform or your own wallet shows the USDT frozen. The trade looked clean on your side: right amount, right seller, confirmed on-chain. The cause sits in the history of the USDT you received, from before the trade started.

A USDT deposit does not arrive in a separate pile you can hand back untouched. TRC-20 and ERC-20 tokens keep one balance per address, so the moment the transfer lands it merges into whatever you already held there. Tether freezes addresses through a multisig process: a freeze is proposed, and it executes once Tether's signers approve it. If that transfer carried tokens from an address that process later targets, the freeze can land on your address once it holds the merged balance. A freeze locks the whole balance at that address, not only the amount you just received.

Checking the seller's wallet on an explorer before you release fiat, and holding payment if anything in that check is unclear, is the one step you control. Below is what our freeze data shows about how the process plays out, and which fields to read on an explorer before the trade settles.

Our tracker flagged 1,082 wallets, and 1,076 were then frozen

Since 14 July 2026, TrustSniffer's live USDT freeze tracker has flagged 1,082 wallets as stablecoin-issuer freeze targets before the freeze executed. Of the 1,081 flagged wallets with a known outcome, 1,076 were frozen by the issuer, a 99.5% hit rate.

The median time between our flag and the freeze is 6 minutes, and the 90th percentile is 3.2 hours: nine in ten of these freezes landed within that window. The wallets flagged this way held $448.4 million between them at the moment the freeze hit.

A freeze on one chain can reach the same key on another

TRON and Ethereum do not move at the same speed. On TRON, we flagged 978 freezes from Tether's multisig proposals, with a median lead time of 5 minutes before the freeze executed. On Ethereum, we flagged 94, with a median lead time of 33 minutes. If you are the one paying fiat, the longer Ethereum window works against you: a seller whose address is already in a pending proposal can still send you USDT during it, and the freeze can reach your address after you have paid.

Four wallets in our record were frozen for a different reason: each was the cross-chain twin of a key the issuer had just frozen on another network. The same private key can control an address on both TRON and Ethereum, so a freeze triggered by activity on one chain can reach the matching address on the other. A P2P trader who checks only the chain the trade happened on can miss that the seller's twin address, on a different network, is already frozen.

Before you release the fiat, run these checks on the wallet

None of this requires our tools. A blockchain explorer shows the same fields we use.

  • Match the network to the explorer. Use Tronscan for a TRON (TRC-20) transfer or Etherscan for an Ethereum (ERC-20) transfer. Searching the sender's address or the transaction hash on either site shows the sender, the recipient, the token contract, the amount and the time of the transfer.
  • Check the token contract against Tether's two official addresses: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token labelled USDT from any other contract is not Tether's USDT, whatever the display name says.
  • Look at the seller's own transfer history on the same explorer page. Two things should stop you: a wallet with only a handful of transfers, or USDT that arrived shortly before your trade from an address you cannot identify. If you see either, cancel the order before you pay, or ask the seller to send from a different wallet.
  • Read the balance after the transfer as one number. TRC-20 and ERC-20 tokens hold a single balance per address, so once the seller's deposit lands there is no way to keep it separate from funds already in your wallet.

Why the freeze record can't warn you about next week's trade

Tether's multisig process publishes freeze proposals before they execute, without the address or the exact amount shown until the freeze actually lands. Our tracker flags the target from the pending proposal itself, which is why our lead is measured in minutes or hours. Before Tether drafts a proposal, no record anywhere names the wallet, so neither our data nor an explorer can tell you about next week's freeze the way it can show you yesterday's.

The freeze tracker shows how often a flagged wallet is frozen and how fast; it cannot show which wallet is next. Running the seller's address through TrustSniffer's wallet checker adds a risk assessment on top of the explorer fields. If the token contract matches Tether's and the transfer history looks ordinary, release the fiat. If either is unclear, hold payment and cancel the order or ask for another wallet.

Related reads: check USDT before accepting a P2P trade walks through the explorer fields for a trade you have not settled yet, received USDT from a blacklisted address covers what to save and who to tell once a flagged deposit has landed, and frozen USDT on Binance separates an exchange hold from a Tether blacklist.

Frequently asked questions

Can the freeze tracker tell me which P2P seller will be frozen next?

No. Until Tether drafts a proposal, nothing names the wallet, and pending proposals hide the address until the freeze executes. The tracker records flags and freezes that already happened, so use it on a seller's address alongside the explorer checks.

Is a P2P trade paid in Ethereum USDT riskier than one on TRON?

Ethereum gives more room. Our data puts the typical delay between proposal and freeze at 33 minutes there and 5 on TRON, so funds already marked for a freeze can still reach you for longer.

What should I do if the seller's wallet looks wrong?

Stop before paying. Back out of the order or request payment from another address, and repeat the contract and history reads on it. A seller who refuses gives you your answer.