How to Check a Transaction Hash When Your Crypto Deposit Is Late

--

If you have ever sent crypto and watched the recipient’s balance stay flat for half an hour, you already know the feeling. Was it lost? Was the address wrong? Did the exchange just freeze it? In ninety percent of those cases the only piece of data that actually matters is the transaction hash — TXID for short. Knowing how to read one and where to find one will save you hours of unnecessary panic.

What a transaction hash actually is

Every transfer on a public blockchain — Bitcoin, Ethereum, Tron, BNB Smart Chain, Solana — is hashed by the network the moment you sign and broadcast it. The result is a fixed-length string of hexadecimal characters: 64 for Bitcoin and Tron, 66 with a 0x prefix for Ethereum and BSC, longer for Solana. That string is what wallets, exchanges and explorers use to look the transaction up. It is unique to that one transfer, and it never changes once the transaction is broadcast.

The names are inconsistent across platforms, which is half of the confusion. Binance calls it TxID. MetaMask calls it Transaction Hash. Etherscan calls it Txn Hash. Tronscan just calls it Hash. Bitcoin Core uses TXID. They are all the same thing.

Why platforms keep asking for it

When a deposit is delayed and you contact support, the very first thing the agent will ask for is the hash. There are two reasons. First, the platform needs to verify that the transfer actually exists on chain — without the hash they would have to manually look through every incoming transaction to your deposit address, which can take hours. Second, the hash is the only piece of data that ties your specific payment to your specific support ticket. Most automated services do this matching by software the moment a hash hits their system.

Where to look in the most common wallets

In Trust Wallet, open the History tab and tap the transaction. You will see a row labelled Transaction Hash with a copy icon next to it.

In MetaMask, open Activity, click the transaction, and use «View on Etherscan». The hash is the long string after /tx/ in the explorer URL.

On Binance, go to Wallet → Transaction History, click the transaction, and the TxID field appears beside the amount. If the field is empty, the platform has not broadcast the transfer yet — it is still being processed internally.

On Bybit and OKX the path is similar: Assets → Funding → Deposit or Withdrawal Records → click the entry → copy the TxID.

How to verify a transaction in an explorer

Pick the explorer that matches the network of your transfer. Bitcoin transactions go on mempool.space or blockchain.com. Ethereum and any ERC-20 token, including USDT-ERC20, go on etherscan.io — the trick with USDT here is that the main Value field will show 0 ETH; the actual USDT amount is below, under ERC-20 Token Transfers. Tron and USDT-TRC20 go on tronscan.org under TRC20 Tokens Transferred. BNB Smart Chain goes on bscscan.com, with the same UI logic as Etherscan.

Paste the full hash into the search field, hit enter, and you will see the status: pending, confirmed, or failed. You will also see the number of confirmations. Most platforms release the deposit after between 1 and 6 confirmations depending on the network and the size of the transfer.

The most common mistakes

People send the wallet address instead of the hash. They are different — the address is where the funds went, the hash identifies the transfer itself. Support cannot help with just an address.

People copy the truncated form they see in the wallet UI — something like 0xa1b2...c3d4. The explorer needs the full string. Use the dedicated copy button in the wallet, not your selection.

People look in the wrong explorer. A USDT transfer on TRON will simply not exist in Etherscan, and a USDT transfer on Ethereum will not exist in Tronscan. Always confirm which network the transfer used before searching.
If the hash shows 0 confirmations for over an hour

The transaction is stuck. On Bitcoin and Ethereum this almost always means the fee was too low — the network is prioritising other transfers. You can wait it out, use Replace-By-Fee to rebroadcast at a higher fee if your wallet flagged the transaction as RBF-replaceable, or use Child-Pays-For-Parent: spend the unconfirmed output in a new transaction with a much higher fee, so miners are incentivised to confirm the pair.

On Tron and BSC stuck transactions are rare and usually mean a missing energy / bandwidth or gas allowance. Top up and retry.

For a longer reference with full screenshots and a complete FAQ on how to check a transaction hash, see the linked guide.