Two separate things can stall a USDT deposit on Binance
A USDT deposit lands in your Binance account and the balance will not move. Two things can cause that. Binance may hold your account during its own review, which leaves nothing on the blockchain. Or Tether may freeze the sending or receiving address on the USDT contract, a public action anyone can look up. Both look the same to you. Only a Tether freeze can be confirmed on a blockchain explorer without relying on what Binance's support message says.
963 wallets flagged since July 14, a 99.6% hit rate
TrustSniffer watches Tether's freeze activity so that anyone with a stuck deposit can see whether, and when, an address was blacklisted. Since 2026-07-14, TrustSniffer has flagged 963 wallets as stablecoin-issuer freeze targets before the freeze executed, and each one is recorded on our live USDT freeze tracker. Of the 961 flagged wallets with a known outcome, 957 were frozen by the issuer, a 99.6% hit rate. The median time between our flag and the actual freeze is 10 minutes, and nine in ten took no longer than 3.2 hours. Between them, the wallets we flagged held $418.3 million at the moment the freeze landed. For your deposit, this shows that a Tether freeze is a public, recorded event. If the address behind your deposit was frozen, the record exists and you can find it.
TRON freezes in 6 minutes, Ethereum takes 33, and freezes cross chains
The two networks do not move at the same speed. On TRON, 873 of the freezes we flagged in advance came from Tether's multisig proposals, with a median lead of 6 minutes between our flag and the freeze. On Ethereum, 80 freezes were flagged the same way, with a median lead of 33 minutes, longer than TRON's 6-minute median.
A freeze can also spread to a second network. One private key can control both a TRON address and an Ethereum address, and we call the second address the cross-chain twin of the first. We flagged 4 wallets as the cross-chain twin of a key the issuer had just frozen on another network, and the issuer then froze them too. If your deposit came from an address frozen on one network, a freeze on its twin is a likely next step.
Checking the deposit's source before you assume either cause
The sender address is the fact to confirm first, before deciding whether Binance or Tether is responsible. Genuine USDT has one token contract per network: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON and 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum. A token calling itself USDT from any other contract is not Tether's USDT.
Made-up example: a deposit came from an address the explorer now lists as blacklisted. The funds on that address will not move for anyone, and Binance cannot release them, because the block sits in Tether's contract and has nothing to do with your Binance account.
- Note the amount and time of the deposit, then find its transaction hash or sender address in Binance's deposit history or the confirmation it sent you. Once the deposit lands, it merges into the wallet's existing balance the same way any transfer does: there is one balance per address, and the new amount is added to whatever was already there. You cannot set the suspect deposit apart while you check.
- Confirm the transfer used Tether's contract (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t on TRON, 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum). A token from any other contract is a lookalike.
- Paste the sender address into Tronscan or Etherscan, matching the network the deposit moved on. Both explorers list the sender, recipient, contract, amount and time for every transfer on that address.
- Look for a blacklist marker on both ends of the transfer: the sender address, and the recipient, which is the Binance deposit address the funds were sent to. A marker on either means Tether froze that address, and the funds would be stuck on any exchange. An ordinary history with no marker means the hold is Binance's own, and only Binance can lift it.
How our freeze record is built, and its blind spot
If you want a single lookup instead of switching between two explorers, TrustSniffer's wallet checker runs the same check and tells you whether the contract shows that address as blacklisted.
The blind spot is timing. Pending proposals are published without their address or exact amount until the freeze executes, so the live tracker cannot warn a holder in time to move funds. Our flags come minutes before a freeze, which makes the tracker a record of what has already happened. That is what you need for a stuck deposit: confirmation of whether an address tied to it was frozen.
If the sender traces to an address the explorer already shows as blacklisted, the freeze sits in Tether's contract, and moving the funds to a different exchange would not change it. If the transfer history is normal with no blacklist marker anywhere, the hold is Binance's own: answer whatever Binance's support asks of you, and Binance decides whether to release the funds after its review. When the result is unclear, treat the cause as unresolved and raise it with Binance support, attaching the transaction hash.
Related reads: USDT frozen meaning explains the blacklist and the exchange hold side by side, exchange froze account after a USDT deposit lists the facts support will ask for, and P2P USDT account frozen covers a freeze that follows a peer-to-peer trade.
