A transaction hash (often called a TXID) is an identifier for an on-chain transaction. Find it in your wallet or exchange activity, then search it on an explorer for the exact network used. Check the transaction status, asset, amount and recipient. A hash alone does not prove that a transfer succeeded or that a receiving service credited your account.
Never enter a recovery phrase, private key or sign-in code into an explorer or support form. An unsolicited person asking for a “release fee” or wallet access cannot make a transaction settle for you. This guide is educational and cannot inspect your payment.
Where do I find my transaction hash?
- Open the sending wallet or exchange’s activity, withdrawal or transaction history.
- Select the specific transfer and look for “transaction hash,” “TXID,” “transaction ID,” or an explorer link. Copy the full value rather than a shortened preview.
- Record the network shown by the sender. “USDT” or “USDC” names an asset, not a network; the same named asset can be sent on more than one chain.
- If the service only shows an internal reference or a withdrawal marked “processing,” it may not have broadcast an on-chain transaction yet. Ask the sending service through its official support route rather than guessing a hash.
Wallet and exchange menus differ. For example, Coinbase’s help page explains how to locate its transaction hash and use a chain-specific explorer. An internal order, deposit or withdrawal ID is not necessarily the on-chain TXID.
How do I check a TXID on a block explorer?
Use the explorer link offered by your own wallet or service, or navigate to a trusted explorer for the network independently. Search the full transaction hash. For a Bitcoin mainnet TXID, the crypto.tt latest Bitcoin blocks page can prepare a link to a Bitcoin explorer; it does not verify the transaction itself. Ethereum and layer-2 transfers need the appropriate network’s explorer. A “not found” result can mean the wrong chain, a hash not yet propagated, a typo or a service that has not broadcast the transaction; it does not by itself tell you which.
On a narrow screen, scroll the table sideways to see all columns.
| Explorer field | What to check | What it cannot prove alone |
|---|---|---|
| Network and transaction status | Is this the actual chain? Is the transaction pending, included, failed or successful? | A pending hash is not a completed payment. If an Ethereum receipt shows failure, read why gas can still be charged. |
| Recipient and amount | Compare the full destination and delivered asset amount with the sender’s record and receiver’s deposit instructions. | Matching the first and last characters of an address is not enough. See address poisoning. |
| Block and confirmations | Check inclusion height and whether the receiver requires more confirmations. | On-chain inclusion is not the same as an exchange credit. |
| Token transfers on EVM chains | For ERC-20 tokens, inspect the token-transfer record, its contract and recipient; the top-level “To” may be a contract. | A successful contract call does not mean the token reached the intended account. |
Ethereum’s transaction lifecycle distinguishes a generated hash, broadcast and block inclusion. Its transaction receipt specification includes the block and a success/failure status. For ERC-20 assets, the token standard’s Transfer event is why explorers often show a separate token-transfers section. Bitcoin’s transaction reference explains confirmation counts.
Worked example: a USDC deposit that has not appeared
Imagine a sender withdraws 100 USDC on Ethereum mainnet. The exchange displays a hash and marks the withdrawal complete. The receiving account still shows no deposit. Search the hash on an Ethereum mainnet explorer. If the transaction is successful, inspect its USDC token-transfer entry: is the token contract the expected one, the destination address exactly right and the transfer amount 100 USDC? Then compare the receiving service’s current USDC-on-Ethereum deposit instructions and required confirmations. The sender’s “complete” label only describes its own workflow; the receiver controls account credit. If there is a mismatch, contact the receiver’s official support with the hash and details; do not send a second payment as a test.
If the same USDC had been sent on another supported chain, an Ethereum mainnet explorer would be the wrong place to assess it. The network is part of the evidence, even when a token name and an address look familiar.
What can I safely share with support?
A TXID is public chain data, so you can usually give it to official sender or receiver support when investigating a transfer. It can expose linked addresses, amounts and transaction history. Share only what is needed: TXID, network, asset, approximate UTC time and relevant support ticket. Never share a recovery phrase, private key, one-time code, remote-control access or an unrequested wallet signature. Keep screenshots cropped if they show balances or personal information.
Common questions
Is a transaction hash the same as a wallet address?
No. A TXID identifies a transaction on one network; a wallet address identifies a destination or account on that network. Do not paste a TXID into an address field or send assets to it.
Does a TXID mean the transaction is confirmed?
No. A hash can exist while a transaction is pending. Check the network explorer for inclusion and status. On Ethereum, a receipt is available after inclusion; on Bitcoin, confirmation count increases as later blocks are added. A receiving service can still have its own crediting requirements.
Why is my hash not found?
Check that the hash is complete and the explorer matches the network. If the sender still shows a withdrawal in progress, there may be no on-chain transaction to find. If it says broadcast but no explorer can locate it, ask the sender through its official support channel. Do not assume a screenshot or a copied hash is proof of payment.
Next step for your situation
Use the pending or missing transfer guide to decide whether the sender, network or receiver is the right next contact. Before a future payment, use the asset, network and recipient checklist. When the asset is USDT or USDC, read the stablecoin comparison for network and issuer considerations. These resources explain the checks; none can recover funds or replace the receiver’s current instructions.
See how crypto.tt sources and reviews guides. Check current network and service instructions before acting.