USDT Sent but Not Received: a TXID Troubleshooting Checklist

If you sent USDT and it never arrived, the first thing to do is find the TXID — the transaction hash — in your wallet's history and open it in a blockchain explorer. From there, exactly four scenarios are possible: the transaction is not found (it never reached the network), it is still unconfirmed, it ended with a FAILED status (most often due to OUT_OF_ENERGY), or it completed with SUCCESS — in which case the funds are already sitting on the recipient's address and the delay is on the exchange's or service's side. This article is a step-by-step checklist: how to identify your scenario in a couple of minutes and what to do in each case.

Step 1. Find the TXID and open the transaction in an explorer

The TXID (also called the transaction hash) is a 64-character string of digits and Latin letters from a to f. It uniquely identifies your transaction on the blockchain. Mobile and browser wallets show the TXID in the transaction details: open your history, select the transfer, and look for a field labeled "Hash", "TXID", or "Transaction ID" — there is usually a copy button next to it. If you withdrew USDT from an exchange, the TXID appears in the withdrawal history once the platform has actually broadcast the transaction.

Step 2. Identify your scenario by transaction status

• "Transaction not found" — the explorer cannot find the TXID: the transaction never reached the network.
• "Unconfirmed" — the transaction is in the network, but its block has not become irreversible yet: wait a moment.
• FAILED — the transaction was rejected: your tokens did not leave, and you need to find and fix the cause.
• SUCCESS — the transfer completed on-chain: if the recipient "doesn't see it", the problem is on the receiving side.

Scenario 1. "Transaction not found": it never reached the network

If the explorer cannot find the transaction by TXID after a few minutes, the network never accepted it. Typical causes: the wallet lost its connection at the moment of sending, the public node the wallet broadcasts through was overloaded, or the app showed "sent" before the transaction was actually transmitted. A separate case is checking the TXID on the wrong network: there is no point searching for a TRC-20 transaction in Ethereum or BNB Chain explorers.

What to do: confirm via your address history in the explorer that no debit actually happened (search for your address, not just the TXID), check your connection, and send the transfer again. Do not re-send until you have confirmed the first transaction did not go through — otherwise you risk paying twice.

Scenario 2. Unconfirmed transaction: how long to wait

The query "trc20 stuck pending" is one of the most common, but in the Ethereum sense it simply does not apply to TRON: there is no gas-price queue you need to push a transaction out of by bumping the fee, and no mechanism for replacing a sent transaction. If your wallet shows pending for more than a few minutes, it is almost always a wallet UI issue, not a network one. Check the actual status in the explorer: most of the time it is already SUCCESS and the wallet just has not refreshed its history. Restarting the app or re-syncing usually fixes it.

Scenario 3. FAILED status: the transaction was rejected

A FAILED status means the smart contract did not execute the transfer: your USDT stayed on your address. The most common cause on TRON is OUT_OF_ENERGY: the address did not have enough energy, and the fee limit (fee_limit) was not high enough to burn the shortfall in TRX. Note that although the tokens did not move, the network may still have charged TRX for the resources actually consumed, up to the fee_limit — that is normal behavior, not a double loss.

Less often, FAILED is caused by a REVERT inside the contract: for example, you tried to send more USDT than your balance holds, or the wallet supplied invalid parameters. The explorer's transaction page shows the rejection reason in the contract execution details.

Scenario 4. SUCCESS, but the exchange has not credited the deposit

This is the most common case behind "usdt not received on exchange" queries. A SUCCESS status means the blockchain did its job: the tokens are recorded on the recipient's address, and the network can no longer cancel or lose them. So the cause must be on the receiving side. Go through this list.

• Network and token: the transaction page must show exactly the token and network the exchange expects. A TRC-20 deposit address always starts with the letter T.
• Recipient address: compare it with the exchange's deposit address in full, character by character, not just the first and last few — clipboard malware is known to swap addresses on copy.
• Minimum deposit amount: many platforms do not credit transfers below a set minimum; the threshold is shown on the deposit page.
• Number of confirmations: exchanges credit deposits after their own required confirmation count; until the counter reaches it, the deposit shows as processing.
• Suspended deposits: during TRC-20 network maintenance, incoming transfers queue up and are credited after deposits resume.
• Internal transactions: if the USDT arrived via a smart contract rather than a direct transfer, some platforms do not credit such deposits automatically — a support ticket is needed.
• Tag or memo: on TRON, deposits are normally identified by address, but some custodial services require a memo — check the rules of your specific platform.

If everything checks out and the credit still has not arrived after a reasonable time, contact the exchange's support. Attach the TXID, a screenshot of the transaction page from the explorer, and the exact time of sending. The funds are physically on the platform's address, so the issue is resolved on their side — it is a matter of time, not a risk of loss.

What not to do

• Do not re-send the transfer until you know the fate of the first one: two SUCCESS transactions mean two debits.
• Do not use "transaction accelerators" for TRON: the network has no acceleration mechanism, so such services are useless at best.
• Do not contact "crypto recovery services" from search results or comment sections — this is a widespread scam pattern.
• Never share your seed phrase or private key with anyone, including "support" that messaged you first: real support never asks for them.
• Do not panic over a pending status in your wallet: the explorer status is primary, the wallet UI is secondary.

The short checklist

• Find the TXID in your wallet history or the exchange's withdrawal history.
• Open the TXID in an explorer and check the transaction status.
• Not found — wait a couple of minutes, check your address history, and send again.
• FAILED — identify the cause (most often OUT_OF_ENERGY), top up resources, and retry the transfer.
• SUCCESS — verify the network, token contract, and recipient address against the deposit details.
• Check the minimum deposit amount and the TRC-20 deposit status on the platform.
• If everything matches — open a support ticket with the TXID and an explorer screenshot.
• For the future: prepare energy before sending to rule out FAILED.

How to avoid this next time

Scenarios 1 and 2 are cured by waiting and re-sending, and scenario 4 by double-checking the deposit details. FAILED due to lack of energy is the only scenario that is fully under your control and can be ruled out in advance: before transferring, make sure your address has enough energy or TRX, and if you are sending to an address that holds no USDT, budget roughly double.