Guides · 6 min read
How to check a USDT transaction on Tronscan or Etherscan
How to check a USDT transaction on Tronscan or Etherscan: find the transaction hash, use the right explorer, read the status, and see what "not found" means.
To check a USDT transaction, copy its transaction hash (TXID) and search for it on the explorer for the network it was sent on: Tronscan for USDT on Tron (TRC-20), and Etherscan for USDT on Ethereum (ERC-20). The page shows whether the transfer succeeded, which address received it, how much moved and what the network charged.
This guide shows how to check a USDT transaction on Tronscan or Etherscan from start to finish: finding the hash, reading the page, and telling what each status means, including "not found".
What a transaction hash is
Every blockchain transaction gets its own ID, generated from the transaction when it's made. Apps call it a transaction hash, a TXID or a transaction ID. It's the same everywhere: in the sender's app, on the explorer and on a receipt.
- A Tron hash is 64 characters, using 0 to 9 and a to f.
- An Ethereum hash is 0x followed by 64 of the same characters.
The hash is public, so it's fine to share with the person you paid or with support. It shows the transfer; it can't move money. Your password, PIN and keys are what you never share.
Where to find the hash in Peppy
Open Activity and tap the transfer. Its details show the network it went on, its status and, once it has one, its Transaction ID, with a button to copy it.
For a completed send, View receipt gives you a PDF receipt to share with the person you paid. It lists the network, the recipient address and the transaction hash, and where to look the transfer up on Tronscan or Etherscan.
On other platforms, look in the transfer's details for a TXID, transaction hash or transaction ID.
Which explorer to use
| Network | Explorer | The hash looks like |
|---|---|---|
| USDT on Tron (TRC-20), TRX | tronscan.org | 64 characters |
| USDT on Ethereum (ERC-20), ETH | etherscan.io | 0x and 64 characters |
Each explorer reads its own network only. A Tron hash finds nothing on Etherscan, and an Ethereum hash finds nothing on Tronscan. If the USDT went out on some other network, its hash belongs on that network's explorer. Not sure which network a transfer used? USDT on Tron or Ethereum shows how to tell.
Type the explorer's address yourself, or use a bookmark. Tron's security guide warns that copies of explorer sites exist to trick people.
How to read the transaction page
Paste the whole hash into the explorer's search box. On the page, check:
- The status. Whether it succeeded, failed or is still on its way. The next section explains each one.
- The token. It should be USDT from Tether's own contract (see Is it really USDT?).
- Who received it. A USDT transfer is a call to the USDT contract, so the transaction's main "to" is often the contract itself. The receiving address is in the token transfer line, with the amount.
- The fee. On Tron it's paid in TRX, and Tronscan breaks it down into energy and bandwidth. On Ethereum it's paid in ETH.
What the statuses mean
| You see | It means |
|---|---|
| Success and Confirmed on Tronscan | The transfer ran, and it's final. |
| Success on Etherscan | The transfer ran. Ethereum makes it final a little later. |
| Unconfirmed on Tronscan | It's in a block that isn't final yet. Tron's docs say blocks usually become final in about a minute. |
| Pending on Etherscan | It's waiting to be put in a block. |
| Fail or Failed | The transfer didn't go through, and no USDT moved. The network still charged for the work done. On Tron the reason may read OUT_OF_ENERGY or REVERT. |
| Dropped, or Dropped & Replaced, on Etherscan | It never made it into a block, so it's as if it never happened. With Replaced, a newer transaction from the same sender took its place. |
On Tron, OUT_OF_ENERGY means the transfer needed more energy than its sender could cover. Why you need TRX to send USDT explains how Tron's fee works.
What "not found" usually means
If the explorer can't find the hash, it's usually one of these:
- The wrong explorer. Check which network the transfer was sent on, and use that network's explorer.
- Part of the hash is missing. Copy all of it, including the 0x on Ethereum.
- It's very new. Explorers can lag the network a little. Wait a minute and search again.
- It hasn't been sent yet. The sending platform may still be preparing or checking it. In Peppy, a send that still shows Preparing has no transaction ID yet, and some sends need a security check before they go out.
- It was dropped. A transaction that never made it into a block isn't on the chain at all. On Tron, a signed transaction that isn't included before it expires is dropped. On Ethereum, a dropped transaction's amount and fee never leave the sender's balance.
Confirmed, but not in the balance yet?
A confirmed transfer has reached the receiving address. Showing it in a balance is the receiving platform's job, and each platform has its own rules:
- It watches certain networks and tokens only. USDT sent on a network it doesn't use won't appear. Sent USDT to the wrong network? explains what that means.
- It waits for its own confirmation point. Peppy credits USDT on Tron once Tron confirms the transfer. On Ethereum it waits for the transfer to reach finality, which takes longer. So a transfer can look complete on an explorer a little before it shows in your Peppy balance.
If the explorer shows the transfer as successful and confirmed, and it still hasn't arrived after a while, contact the receiving platform and give them the hash. In Peppy, open Help & support (Settings, then Help & support) and include the transaction ID.
Is it really USDT?
A token's name is chosen by whoever creates it, so a token called USDT isn't always USDT. Tron's security guide warns about scam tokens that copy real names. Real USDT comes from Tether's own contracts, which Tether lists on its website:
- USDT on Tron:
TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t - USDT on Ethereum:
0xdac17f958d2ee523a2206206994597c13d831ec7
On the transaction page, the token's contract should match. Etherscan may show some of the Ethereum address's letters as capitals; it's the same address. Peppy counts only these two contracts, so a look-alike token never shows up as USDT in your balance. How to spot crypto scams covers other tricks to watch for.
Good to know
- An explorer shows what happened; it can't change it. Confirmed transfers can't be reversed.
- Explorers are public. Anyone with the hash can see the addresses and the amount.
- Peppy never asks for your password, PIN or private keys. To ask about a transfer, share its transaction ID.
- Peppy is not a bank, and balances in Peppy aren't bank deposits.
In the Peppy app, Activity has the transaction ID of every transfer that has one. Or read why you need TRX to send USDT, which explains the fee you'll see on Tronscan.
