USDT not showing in your wallet after someone sent it has four distinct causes, and they need opposite responses. Three are recoverable. One is not. Guessing wastes a day messaging support. The answer is on-chain, in thirty seconds.
The single question that splits the cases: are the tokens on the TRON blockchain at your address, or not? Everything else follows from that.
Step one: check the chain, not the app
Your wallet app is a viewer. It can be wrong, out of date, or simply not configured to display a token that is genuinely there. The chain is the record.
Open TRONSCAN, paste your receiving address (not the transaction hash), and open the TRC-20 transfers tab. Then read the result:
| What you see | What it means | Recoverable | | — | — | — | | The transfer, marked SUCCESS | Tokens are yours; this is a display problem | Yes | | The transfer, marked FAILED / OUT_OF_ENERGY | It never completed; the sender still has the tokens | Yes, by the sender | | No transfer at all | It did not happen on TRON | Depends on where it went | | Transfer present, but the balance will not move | The address may be blacklisted | No |
If you have the transaction hash from the sender, search that instead — it tells you the destination address, which is how you catch a typo or a wrong-network send.
Case 1: USDT not showing, but it is on-chain
This is the most common cause of USDT not showing, and the least alarming. TRC-20 tokens do not appear automatically in every wallet. The app has to know to display that contract.
Fix, in order of effort:
1. Pull to refresh, then close and reopen the app. Wallets cache balances. 2. Add the token manually. The USDT TRC-20 contract is `TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t` — verify it character by character against TRONSCAN, because fake token contracts with similar names exist. 3. Confirm your wallet is on the TRON network, not an EVM chain view of the same seed phrase.
The tokens were never at risk. TRONSCAN showing them at your address is the authoritative answer regardless of what the app displays.
Case 2: your address has never been activated
A TRON address does not exist on-chain until something creates it. You can generate one offline. It stays a mathematical fact, not a ledger entry, until its first inbound transaction pays to register it.
Two different fees do that, and confusing them is why you see both “0.1 TRX” and “1 TRX” quoted for activation:
- `getCreateAccountFee` = 100,000 sun (0.1 TRX) — when the sender covers creation with bandwidth.
- `getCreateNewAccountFeeInSystemContract` = 1,000,000 sun (1 TRX) — when the account is created inside a contract call, which is what a TRC-20 transfer is.
Both read live from chain parameters on 20 July 2026. The practical effect for a receiver: an unactivated address can still be credited, but until activation completes some wallets show nothing. Your tokens are not lost. Sending a small amount of TRX to the same address, or waiting for the contract-level creation to settle, brings it into view.
This is also why sending USDT to a brand-new address costs the sender roughly double — around 130,000 Energy instead of 65,000, because the contract has to write a balance record that did not exist. The wallet activation guide covers the sender’s side.
Case 3: the transfer never completed
If TRONSCAN shows the transaction as FAILED — usually with `OUT_OF_ENERGY` — the sender’s wallet ran out of Energy mid-execution. TRON does not refuse such a transaction up front; it executes until resources run out, then reverts.
The consequence is asymmetric and worth telling the sender plainly: the USDT never moved, but the TRX they burned getting that far is gone. They need to supply Energy and send again. A standard USDT transfer needs about 64,285 Energy, or roughly 130,000 to an address that has never held USDT — see what a USDT transfer actually costs, and why TRON transactions fail for the full failure taxonomy.
If they send in volume, renting the resource on the TRON energy market avoids repeating this, since burning TRX is the most expensive way to pay for a transfer.
Case 4: USDT not showing movement because it is frozen
This is the case the other troubleshooting guides skip, and the only one with no fix.
Tether can blacklist any TRC-20 address at the contract level. A blacklisted address still shows its USDT balance on-chain, still sends TRX, still stakes and votes — but the USDT cannot move, in either direction. Nothing about the wallet looks broken until a transfer is attempted.
Anyone can check this for free by calling `isBlackListed` on the USDT contract; the blacklist check walkthrough shows both the TRONSCAN route and the API call. If it returns true, no wallet setting, support ticket or private key changes the outcome — the control belongs to the token issuer, not to the TRON network.
The one genuinely unrecoverable mistake
If TRONSCAN shows nothing at your address, the tokens were not sent on TRON. The usual cause is a network mismatch: the sender chose ERC-20 or BEP-20 while you gave a TRON address, or pasted a TRON address into a form expecting a different chain.
Where they ended up depends on the chains involved, and on whether anyone controls the destination address. If the sender used a centralised exchange, contact it first. Exchanges sometimes recover mis-routed withdrawals, and they are the only party who can. There is no TRON-side fix, because nothing reached TRON.
FAQ
How long should I wait before worrying? TRON blocks are about three seconds. If TRONSCAN shows SUCCESS, waiting longer changes nothing — it is a display issue. If it shows nothing after ten minutes, the transaction was never broadcast.
The sender says it was sent but shows no transaction hash. Then it very likely was not broadcast. A completed TRON transaction always has a hash, and it is always visible on TRONSCAN.
USDT not showing in my app but visible on TRONSCAN — which is right? Add the token contract manually and refresh. Trust TRONSCAN over the app; the app is reading the same chain with its own cache and token list.
Can I recover USDT sent to the wrong network? Not from the TRON side. If a custodial exchange sent it, ask them. If it went to a self-custody address on another chain that you control, import the same seed there.
`getCreateAccountFee` (100,000 sun) and `getCreateNewAccountFeeInSystemContract` (1,000,000 sun) were read from TronGrid chain parameters on 20 July 2026, and the ~64,285 Energy figure was measured directly against the USDT TRC-20 contract at `TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t` the same day. Transaction status should be verified on TRONSCAN, the canonical TRON explorer.
