TxSonar

I sent USDT on the wrong network

Your tokens are not lost. They are at the address you sent them to, on the chain you sent them on. Nothing has been destroyed, and the transaction succeeded — that is precisely why the exchange shows nothing.

USDT is not one thing. It is issued separately on Ethereum, Tron, BNB Chain, Solana, Arbitrum and a dozen others, and those balances are unrelated to each other. An address can be identical across two EVM chains and hold a different amount on each. Sending “USDT” to the right address on the wrong chain puts real tokens somewhere real, just not somewhere the recipient is watching.

Which network did it actually go out on?

The check names the network, the amount and the recipient — and, if you say which exchange you were sending to, whether that exchange credits deposits on that network at all.

Check your transaction

What happens next depends on the recipient

  • Your own wallet. Add the network, import the token, and it is there. Nothing needed from anyone, no fee beyond gas.
  • An exchange that supports that chain. Often it simply arrives late. Their crediting rules and confirmation counts are their own.
  • An exchange that does not support that chain. This is the real case. The tokens are at their address, and only they can move them — through their published retrieval process, at their published price.

Which networks each exchange credits

Read from each exchange's own published deposit list. Where an exchange does not publish one machine-readably it is absent here rather than guessed at — the whole point of this data is that it is not inferred.

All 11 exchanges, side by side · what each charges to retrieve one

The mistakes that produce this

BEP-20 sent to an ERC-20 address
The address is valid on both, so nothing warns you. The tokens are on BNB Chain. If the recipient controls that address themselves, they can reach them by switching network — if it is an exchange deposit address, they cannot without their own process.
TRC-20 sent to an Ethereum address, or the reverse
These address formats are incompatible — Tron addresses start with T, EVM with 0x — so the send usually fails outright rather than going somewhere wrong. When it does go through, the destination was a valid address on the chain used.
The exchange listed the network, but not for deposits
A network you can withdraw to is not always one they credit deposits from. This catches careful people, and it is why the lists above count deposit support specifically.

Do not send a second one

The instinct is to try again on the right network. Do that only after you have the first one settled: if the exchange later credits both, fine, but if it credits neither you have doubled the amount stuck at an address you do not control, and most retrieval fees are per request.

If that was not your case

If the transfer reached an exchange and was never credited, the answer depends on that exchange's own rules: what each exchange does about it.

No wallet connection. No seed phrase. Read-only — we never ask for one, and no legitimate service ever will.