USDT Transfer Not Received? How to Check TRC20 and BEP20 Transfers on Tronscan and BscScan

When a USDT transfer has not arrived, use the TxHash on Tronscan or BscScan to check the on-chain status, then verify the receiving address, network and token contract. This guide covers TRC20 and BEP20 in 6 steps, with a results table and a support checklist.

Published on 2026-11-02 · About 33 min read · Checking Transactions

A USDT transfer shows as sent but the recipient has not received it, so how do you find out what happened? The most direct method is to get the TxHash of the transfer and confirm its status in the block explorer of the correct chain. Once you have an account on the Binance Official Site and the Official Binance App installed, transfers on the TRC20 network are checked on Tronscan and transfers on the BEP20 network are checked on BscScan; iPhone users can follow the site's iOS installation tutorial first. A block explorer only displays public on-chain data. The result shows which address the funds reached, but it cannot replace the handling done by the exchange or wallet provider.

First decide which kind of "not received" problem it is

A USDT transfer that has not arrived usually falls into one of five categories: the transaction is not yet confirmed on-chain, the funds arrived but the exchange has not credited them, the wrong network was selected, the wrong address was entered, or the token contract is not the genuine one. Identifying the category first tells you which explorer to open and what to look for, and saves a lot of detours.

Situation Typical symptom On-chain record? Next step
Transaction not confirmed Wallet shows "sending"; explorer finds nothing or shows pending Possibly none, or pending Wait, and confirm that enough fee resources are available
Confirmed on-chain, not credited by the platform Explorer shows success; the platform's deposit history is empty or processing Yes, status success Verify the receiving address and network, then check the platform's deposit history
Wrong network Sent on TRC20 to an address that belongs to BEP20 (or the reverse) Yes, but on another chain Check the explorer for the matching chain and contact platform support
Wrong address Funds left the wallet but the recipient is not the intended address Yes, with a different recipient Verify the address and contact the receiving platform or the address holder
Wrong token contract The token received only looks like USDT Yes, but the contract is not the official USDT Verify the contract address and do not interact with that token further

Of the five categories, the second is the most common: the transfer has already succeeded on-chain, and the exchange is still waiting for block confirmations or the deposit record needs a manual refresh.

What to prepare before you look anything up

At minimum, prepare four items before checking: the TxHash, the receiving address, the transfer network and the amount. The TxHash matters most, because it leads straight to that specific transfer.

  • TxHash (transaction hash): copy it from the "withdrawal history" or "transfer history" of the sending wallet or exchange.
  • Receiving address: the address shown on the exchange's deposit page or in the recipient's wallet.
  • Network: TRC20 (the TRON network) or BEP20 (BNB Smart Chain, BSC for short), which must match the network the recipient requires.
  • Amount and time: used to compare against the on-chain record.

When the sender is an exchange, the withdrawal history normally shows the TxHash, network and receiving address together. Some platforms have no TxHash yet right after a withdrawal is submitted. That means the platform has not broadcast the transaction, so finding nothing in the explorer is normal and the record needs time to update.

Step 1: Confirm which chain the transfer used

A TRON address starts with a capital T and has 34 characters; a BSC address starts with 0x and has 42 characters. The address format helps identify the chain directly, with no need to guess from memory.

Item TRON (TRC20) BNB Smart Chain (BEP20)
Address format Starts with T, 34 characters Starts with 0x, 42 characters
TxHash format 64 hexadecimal characters, no 0x 0x followed by 64 hexadecimal characters
Matching explorer Tronscan BscScan
Fee payment Paid in TRX or through energy and bandwidth resources Paid in BNB
USDT standard name TRC20 BEP20

The ERC20 USDT on the Ethereum network uses the same address format as BSC, which also starts with 0x, so the address alone cannot tell BSC from Ethereum. For an address starting with 0x, rely on the network chosen when sending, or paste the TxHash into BscScan and Etherscan one after the other.

Step 2: Check a TRC20 USDT transfer on Tronscan

Paste the TxHash into the Tronscan search bar to open the detail page of that TRC20 transfer. The detail page shows the transaction result, the block, the time, the sender, the recipient and the token transfer information.

Items to verify:

  1. Transaction result: the page states whether the transaction succeeded. Success means the contract call was executed. Failure means the transfer did not take effect and the USDT never left, so check the balance back in the wallet.
  2. Token transfer information: a TRC20 USDT transfer normally appears in the section covering token transfers. Verify that the receiving address and the amount match what was intended.
  3. Confirmation status: the page shows the block height and confirmation progress. A transaction that was just broadcast may need a short wait.
  4. Contract address: the official TRC20 contract address of USDT is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t, which can be cross-checked against the information published by Tether.

Without a TxHash, search the receiving address on Tronscan, open the address detail page, view the TRC20 transfer records and find the transfer by time and amount.

Step 3: Check a BEP20 USDT transfer on BscScan

Paste the TxHash into the BscScan search bar to see the status, the recipient and the token transfer details of that BEP20 transfer. BscScan belongs to the same family of products as Etherscan, so the page structure is similar.

Items to verify on the BscScan detail page:

  1. Status: success means the transaction was included and executed. Failure means it was reverted, so the USDT stays at the original address and only the fee was spent.
  2. From and To: the To field is usually the token contract. The real recipient is the receiver listed in the token transfer details.
  3. Token transfer details: check the token name, the amount and the receiving address, and click the token name to confirm the contract address.
  4. USDT contract address on BSC: the BEP20 USDT contract address is 0x55d398326f99059fF775485246999027B3197955, which can be cross-checked against the information published by Tether.

If the status is Pending, the transaction is still waiting to be included in a block. A common cause is a gas price set too low. In that case, use the speed-up option in the wallet or wait for the network to process it.

Step 4: Verify the receiving address, token contract and amount

Once the chain shows success, the receiving address, the token contract and the amount must all be verified, and only when all three match is it certain that the funds reached the intended account. Seeing the word "success" alone does not mean the money arrived in the right place.

Item How to verify What a mismatch means
Receiving address Compare the receiver in the explorer with the deposit page address character by character, paying attention to at least the first 6 and last 6 characters The address was entered wrongly, or altered by clipboard software when pasted
Token contract Click the token name and check whether the contract address is the official USDT The token received is an imitation, not real USDT
Amount Compare with the transfer amount, watching the decimals A different amount may mean a fee was deducted or the wrong quantity was sent
Network The explorer's chain matches the network the recipient requires The wrong network was used, so the asset sits on another chain

Do not compare only the first few characters of an address. Some scams use "address poisoning": the victim receives a tiny transfer so that a look-alike fake address appears in the transaction history, tempting the victim to copy the wrong address next time.

Step 5: Compare against the exchange's deposit record

When the chain shows success and all four items match but the exchange has still not credited the deposit, the problem usually lies on the exchange side, in the confirmation count, the network recognition or the address matching. The next move is to compare against the exchange's deposit record.

In the Official Binance App, open the deposit page, choose USDT, select the same network as the sender (for example TRC20 or BEP20), verify the deposit address shown and view the deposit history. Follow what the Binance App currently displays, because menu names may differ slightly between versions.

A deposit record on an exchange usually has one of several statuses:

  • Processing or confirming: the exchange is waiting for the required block confirmations, which can take from a few minutes to longer depending on network congestion and platform rules. Follow the number of confirmations shown on the Binance page.
  • Completed: the asset has been credited and can be viewed in the spot or funding account.
  • No record: the address or network may not match, or the amount may be below the platform's minimum deposit, which should be checked against the minimum shown on the Binance page.

Step 6: Decide the next move from the on-chain result

Each on-chain result calls for a different action, and identifying the result before acting avoids sending a duplicate transfer. Until the cause is confirmed, do not send again by the same method.

On-chain result Meaning Suggested action
TxHash not found The transaction may not be broadcast yet, the chain may be wrong, or the TxHash was copied incompletely Confirm the status with the sender, then try the explorer of the other chain
Status is failed The transaction was not executed and the USDT is still at the original address Check the balance, top up the fee resources and send again
Status is pending The transaction is waiting to be included Wait, or use the speed-up option in the wallet
Success and address correct The asset reached the intended address Contact the receiving platform with the TxHash and ask it to check the crediting
Success but address wrong The asset went to a different address Trace where the address came from and contact the other party or the platform; recovery depends on the address holder
Success but contract is not official USDT The token received is a different token Do not click token-related links or approve anything

Can funds sent to the wrong network or address be recovered?

Whether funds sent to the wrong network or address can be recovered depends on who controls the receiving address, because the on-chain record itself cannot be reversed. Once a blockchain transfer is confirmed it is irreversible, and no institution can pull a transaction back on-chain.

There are two situations:

  • The receiving address belongs to an exchange or platform: some platforms offer a manual handling channel that requires the TxHash, the network used and the amount. Whether it is possible, whether a fee applies and how long it takes depend on the platform's policy, so follow the current help center instructions of platforms such as Binance.
  • The receiving address belongs to a personal wallet: the funds can only come back if the address holder sends them back voluntarily, and nobody can force it.

One point deserves special attention: anyone who claims to "recover your assets" and asks for an upfront fee, a private key or a seed phrase is almost certainly running a scam.

What to provide when contacting support

When contacting the platform's support, providing the TxHash, network, receiving address, amount, transfer time and explorer screenshots speeds up the investigation considerably. With complete material, support staff do not need to keep asking follow-up questions.

It helps to prepare a checklist in advance:

  1. The name of the sending platform or wallet, and the time of the transfer;
  2. The complete TxHash (never shortened);
  3. The network used (TRC20 or BEP20);
  4. The full receiving address;
  5. A screenshot of the Tronscan or BscScan detail page, showing the status and the token transfer details;
  6. A screenshot of the deposit page showing the address and network.

Risks and security reminders

Never enter a private key or seed phrase during a lookup, because a block explorer never asks users for such information. Any "query page" that asks for a seed phrase should be treated as a phishing site.

  • Check the spelling of the domain before opening an explorer from a bookmark or a search result, to avoid imitation pages;
  • Do not click "arrival check" links sent by strangers;
  • Do not authorize unknown websites to connect to the wallet, since an authorization can lead to assets being drained;
  • Before a large transfer, send a small test amount first and send the rest only after it arrives;
  • Crypto trading carries risk. Users in mainland China should follow local laws and regulations. This site is an independent third-party tutorial site and does not give investment advice.

FAQ

Q: The USDT transfer shows success but the exchange has not credited it. What should I do? A: First verify the receiving address, network and token contract on Tronscan or BscScan. If all three match, the asset has reached the exchange's address, and the next step is to contact the platform's support with the TxHash so that it can check the crediting.

Q: Why can't I find the TxHash in the explorer? A: Common causes are an incompletely copied TxHash, the explorer of the wrong chain, or a transaction that has not been broadcast yet. Try the explorer of the other chain, and go back to the sender to confirm that the record already has a TxHash.

Q: Can USDT on TRC20 and BEP20 be transferred to each other directly? A: No. USDT on the two chains consists of separate contract assets. If it is sent to an address of the other chain, the asset stays on the chain used for sending and the recipient cannot see it.

Q: How long does a Pending status on BscScan last? A: There is no fixed duration. It depends on the gas price and network congestion. If it stays unconfirmed for a long time, use the speed-up function in the wallet or wait for the network to process it.

Q: If the chain shows failed, is the USDT lost? A: No. A failed transaction did not carry out the transfer, so the USDT remains at the original address and only the fee is spent. Check the balance in the wallet and send again.

Q: Can funds sent to the wrong network be recovered? A: It depends on whether the platform controls the receiving address. A platform address may support manual handling, which requires the TxHash and other material, and whether it is feasible and how long it takes follow the platform's own instructions. For a personal wallet address, recovery depends entirely on the other party sending the funds back.

Q: How can I tell whether the USDT received is the official one? A: On the explorer detail page, click the token name and check whether the contract address matches the contract published by Tether. A token with the same name and icon is not necessarily the official USDT.

Summary

When a USDT transfer has not arrived, get the TxHash first, choose Tronscan or BscScan according to the chain, verify the status, receiving address, token contract and amount, and finally compare against the exchange's deposit record. To keep checking the deposit account, sign in to the Binance Official Site and review the deposit history.