What Is a Transaction Hash?

BeginnerNov 2, 2026 · 7 min read

A transaction hash is the unique receipt and lookup identifier for a submitted blockchain transfer. After you send, withdraw, deposit, or swap, the network (and most wallets or venues) give that attempt an ID so you can find that exact transfer later.

Definition

A transaction hash is the unique receipt and lookup identifier for a submitted blockchain transfer.

After you send, withdraw, deposit, or swap, the network (and most wallets or venues) give that attempt an ID so you can find that exact transfer later. It is proof-of-submit material. It is not the destination, not the network name, and not the explorer tool itself.

In plain English:

A transaction hash is the receipt ID for one submitted transfer. Copy the full string to check status or prove a send. It does not move funds by itself, and it does not reverse a transfer.

The hash is usually created from the transaction’s data — a fingerprint of that one attempt. You do not need the hashing math. You need to recognize the field, copy it cleanly, and use it for status and support.

In Trading

When you meet it (three scenes traders recognize)

Wallet Activity / History

After a send, receive, approve, or swap, open Activity or History. Each row is usually one attempt. Open the row and look for Transaction ID, Tx Hash, or Hash, plus a copy control. Many wallets also show View on explorer / View on Solscan (or a similar network-linked label). That link rides on the hash — the hash is still the identifier you may need to paste into a support ticket.

CEX withdraw / deposit history

On a centralized exchange, open withdraw or deposit history (sometimes under Assets → History, Transaction History, or Funding). Once the venue broadcasts an on-chain transfer, the detail panel usually exposes a TXID / Transaction Hash. That string is what you use to track the transfer outside the venue and what support teams ask for when a deposit is late.

DEX toast / activity after a swap

After you confirm a swap (or similar on-chain action) in the wallet, the DEX or dApp often shows a short toast — “Transaction submitted,” “Pending,” or “Success” — with a hash snippet or a View transaction / explorer link. The same ID also lands in wallet Activity. The toast is not a second transfer; it is another window onto the same receipt ID.

If you have traded for a week, you have almost certainly met at least one of these screens.

Names and forms you will see (same job)

Different apps label the same receipt ID differently. Treat these as synonyms for one user job: look up this submitted transfer.

Label you may see	What it usually means
Transaction hash / Txn hash / Tx Hash	The on-chain receipt / lookup ID
TXID / TxID / Transaction ID	Same job — common on exchanges and support forms
Hash (alone in a detail panel)	Usually the transaction hash in context of that row
Signature (common on Solana screens)	Same receipt/lookup job under a different chain label
Long hex string (often 64 hex characters; Ethereum-style screens often show a `0x` prefix)	Appearance recognition only — encodings differ by network

You are not collecting different “kinds” of money IDs. You are learning the screen vocabulary for one receipt.

Tiny contrast that saves support time:

Transaction hash / TXID — identifies one on-chain attempt.
Order ID / withdrawal ID — venue-internal reference; useful inside that venue, but not a substitute for an on-chain TXID on an explorer.
Wallet address — destination or account string (see What Is a Wallet Address?).

Status light after submit

Status you may see	What it usually means
Pending / submitted	Broadcast (or queued) but not yet included as a successful settlement
Success / confirmed	Included on-chain; more confirmations deepen settlement confidence
Failed	An attempt was recorded, but the intended transfer did not complete
Dropped / replaced	The pending attempt did not stick, or a replacement took its place (recognition only)

Venues may wait for several confirmations before they credit a deposit. “Seen in wallet as pending” is not the same as “credited on the venue.” A failed attempt can still leave a hash — the receipt of a try that did not complete as intended.

Worked example: what happens in order after a send / withdraw / swap

Recognition walkthrough (generic flow — not a brand button checklist):

You submit a send from a wallet, a withdraw from an exchange, or a swap on a DEX and confirm in the wallet.
Look for the receipt surface: Activity / History, withdraw/deposit history, or the post-submit toast.
Open the row or detail panel. Find the field labeled Transaction ID, TXID, Tx Hash, or Hash.
Copy the full string with the copy control. Do not retype from a truncated preview. Prefer the full string over a blurry screenshot when you contact support.
Read the status light on that same screen — pending, success/confirmed, or failed.
Only if you need more detail, open View on explorer or paste the hash into an explorer for the same network the transfer used. The hash is the lookup key; the explorer is the viewer.
If a venue should credit you, check credit state separately from on-chain status. A success hash does not automatically mean the venue has credited the deposit.

That order is the whole point: find the receipt → copy it clean → read status → deepen in the matching-network explorer only if needed.

What you can and cannot do with a transaction hash

Can

Look up one specific submitted transfer later.
Read status at recognition level — pending, success, or failed.
Prove a send to a counterparty, accountant, or support desk by sharing the full hash (or the official explorer link built from it).
Separate “broadcast happened” from “I have no idea where the transfer went.”

Cannot

Move funds by pasting or sharing the hash. The hash is an ID, not a payment instruction.
Reverse a confirmed transfer. Confirmed on-chain results are typically final; a hash documents them, it does not undo them.
Guarantee venue credit. On-chain success and exchange/app credit can diverge.
Replace destination, network, or fee checks you should have finished before submit.
Stand in for a private key, seed phrase, or signature authority.

Copy hygiene and proof of send

Copy the full hash. Truncated strings usually fail lookup.
Prefer copy/paste over screenshots when support needs the ID.
Paste into the explorer for the same network the transfer used.
Share the hash (or official explorer link) when you need proof of send or support evidence.
Never confuse “share the hash” with “share a seed phrase or private key.” The hash is public lookup material on transparent chains; secrets are not.

What usually goes wrong

No TXID yet after a CEX withdraw — often still internal processing, or an internal/off-chain move that never creates an on-chain hash. Check history before assuming loss.
Still pending for a long time — fee / congestion / replacement territory; status recognition first, not panic rewriting. Fee depth lives on What Is Gas Fee?
Failed attempt — the hash may still exist as a record of the failed try.
Confirmed on-chain but not credited — different failure from “no hash”; venue credit rules and network match still matter.
Pasted into the wrong-network explorer — lookup misses even when the hash is real.
Shared a truncated string or only an order ID — support and explorers cannot resolve the on-chain attempt.

How to judge right after you submit

Did a transaction hash / TXID appear in wallet Activity/History, venue history, or the DEX toast?
Can I copy the full string, not a truncated preview?
What status light does it show — pending, success, or failed?
If I need more detail, am I opening an explorer for the same network?
If a venue should credit me, does history show the hash and the credit state separately?

If you later move funds involving edgeX, use the official history / deposit screens first. Keep the TXID from your wallet or sending venue so you can track status without guessing.

For destination checks, see What Is a Wallet Address? For the settlement environment, see What Is a Blockchain Network? For reading explorer pages in depth, see What Is a Block Explorer? and How to Use a Block Explorer.

Don’t Confuse With

Transaction hash ≠ wallet address. The address is where funds should arrive. The hash identifies one submitted transfer.
Transaction hash ≠ blockchain network. Network is the ledger environment. The hash is an ID inside that environment’s history.
Transaction hash ≠ gas fee. Fee is what you pay for inclusion. The hash is the receipt ID after submit.
Transaction hash ≠ block explorer. The explorer is a viewer. The hash is the lookup key you paste into it.
Transaction hash ≠ private key / seed / signature authority. Signing authorizes the transfer. The hash labels the submitted result.
Having a hash ≠ guaranteed venue credit. On-chain success and venue credit can diverge.
TXID ≠ venue order ID / withdrawal ID. Internal references help inside one venue; they are not the on-chain receipt unless the screen also shows a blockchain TXID.

Ready for the next step?

Continue to registration or trading from this page using the official links.

Start trading on edgeX

Disclaimer

This content is for educational purposes only and does not constitute investment advice. Trading digital assets and derivatives involves risk. Make sure you understand the products and consider your own circumstances before trading.