Find the receipt behind the transaction hash
An Ethereum transaction can call a contract and produce several event logs. The transaction recipient identifies the account called by the top-level transaction. The receipt’s logs identify contracts that emitted events during execution. Ethereum’s JSON-RPC reference documents the receipt fields, and ERC-20 specifies the Transfer event for compatible tokens. [1] [2] Start with the intended network and exact transaction hash before looking for the payment inside those logs.
Check which contract emitted the event
Imagine a swap where an explorer shows one token leaving a wallet and a second arriving. Match the incoming Transfer log to the expected token contract and to the full recipient address. Decode the amount using the token’s actual decimals where applicable. For example, 2,500,000 raw units represent 2.5 units if that contract uses six decimals. A familiar token symbol alone can refer to a different contract. Compare raw token amounts with their display units and inclusion with finality.
Reconcile the receipt with the receiving platform
A valid on-chain transfer and a credit in an exchange account are different records. If a transfer appears on-chain and the platform balance remains unchanged, note the network, transaction hash, emitting contract, recipient and amount before contacting support through the platform’s official channel. That packet is sufficient to describe the transfer without sharing wallet secrets. An explorer’s summary line is useful for navigation, while the emitting address and log data identify the recorded event.

Crypto in the UAE
Explore the UAE digital asset landscape.
Discover the book ↗Read the book overview →Sources & further reading
Sources consulted 13 November 2026. Editorial frameworks and illustrative examples are identified within the text.



