What the hash lets you do
Paste it into a block explorer for the right network and you see the whole transfer: sender, recipient, amount, fee, timestamp, and how many confirmations it has collected.
That is the entire point. The hash is a public receipt that neither side can forge or alter, and anyone holding it can verify the same facts independently.
Where to find it
Every wallet shows it, though the label varies: transaction ID, TXID, hash, or sometimes just an entry you tap to expand. Exchanges list it in the withdrawal history next to each outgoing transfer.
If a payment came from an exchange rather than a personal wallet, the hash still exists and the sender can retrieve it. This matters, because it is usually the fastest way to settle a payment dispute.
What a hash does not prove
Two things people routinely assume it does.
It does not mean the payment arrived. A hash exists as soon as the transaction is broadcast. Until the network confirms it, the transfer can still fail, be replaced by a version with a higher fee, or sit unconfirmed for hours.
It does not mean the right amount went to the right place. The hash identifies a transaction; it says nothing about whether that transaction matched the invoice. Open it and check the destination address and the amount against what was expected.
How merchants use it
The most common support exchange in crypto payments runs like this. A customer writes that they paid and the order has not updated. The merchant asks for the hash. Thirty seconds in an explorer settles which of four things happened: the transfer is still confirming, it went to the wrong network, the amount was short, or it never left the sender’s wallet.
Without a hash the same conversation takes days and usually ends in a refund nobody owed.
A payment gateway does this automatically. It watches for the transfer, matches it to the order, records the hash against the payment and updates the order status without anyone being asked for anything.