A block explorer transaction page shows: status (success/fail), the block it was included in, sender and receiver addresses, value transferred, gas used and fee paid, and input data (what function was called on a smart contract). Learning to read these fields takes five minutes and lets you verify any transfer, debug failed transactions, and confirm DeFi interactions independently.
How to Read a Block Explorer Transaction
3 min read
The short version
A block explorer is your receipt for every on-chain action. When someone says check the transaction on Etherscan, they mean go look at the permanent public record and verify what actually happened. Once you know which fields to look at, you can answer: did my transfer go through? How much did I actually pay in fees? What did that contract call do?
How It Works
Key fields on an Etherscan transaction page, in order: Transaction Hash (TxHash): the unique ID for this specific transaction. Use this to find it again or share proof of payment. Status: Success (green checkmark) or Fail (red X). Failed transactions still consume gas but do not execute their intended action. Block: which block included this transaction. Higher block number = more recent. Confirmations = blocks mined since. From: the address that signed and sent the transaction (paid the gas). To: the recipient address. For contract interactions, this is the contract address, not the final destination of tokens. Value: ETH transferred with this transaction (can be 0 for token transfers or contract calls). Transaction Fee: total gas cost in ETH and USD. Calculated as gas_used x gas_price. Gas Price: what this transaction paid per unit of gas (in gwei). Gas Limit & Usage: maximum gas allocated vs. actually consumed. If usage hits the limit, the transaction ran out of gas and failed. Input Data: for smart contract calls, this shows the function selector and encoded parameters. Etherscan decodes common functions (transfer, approve, swap) into readable format.
Reading a real Uniswap swap transaction
You swapped ETH for USDC on Uniswap and want to verify. Find the TxHash in your wallet activity and paste it into etherscan.io. You see: Status: Success. From: your wallet address. To: Uniswap V3 Router (0x68b3465833fb72A70ecDF485E0e4C7bD8665Fc45). Value: 0.5 ETH (what you sent to the router). Transaction Fee: 0.003 ETH ($9.00). Under Tokens Transferred tab: 0.5 ETH moved from you to the pool, and 1,497.5 USDC moved from the pool to you. The Input Data (decoded) shows: swapExactETHForTokens with parameters for minimum output and deadline. Everything checks out: you sent 0.5 ETH, received 1,497.5 USDC, paid $9 in gas.
What People Get Wrong
The To field always shows who received my tokens
For contract interactions, the To field is the contract address (like Uniswap Router). The actual token movement is shown in the Tokens Transferred section or Internal Transactions tab. The To field shows who you talked to, not necessarily who ended up with value.
A failed transaction means nothing happened
Failed transactions still consume gas (you still paid the fee). The state changes are reverted but the gas payment is not. This is why you see charges for failed transactions in your wallet history.
High gas usage means I overpaid
Gas usage reflects how much computation the transaction required. A simple ETH transfer uses 21,000 gas. A complex DeFi interaction might use 300,000. The usage itself is not waste; it represents actual work. What you control is the gas price (how much per unit), not the usage (how many units the operation needs).
Keep Reading
Sources & Further Reading
- Etherscan
Ethereum block explorer for looking up any transaction
- Mempool.space
Bitcoin transaction explorer with fee estimation and mempool visualization
Questions People Also Ask
- How do I find my transaction hash?
- In MetaMask: click the transaction in Activity, then View on Explorer. In Coinbase: check withdrawal history for the TxHash. In any wallet: the hash is provided immediately after you send a transaction. You can also search by your wallet address on the explorer and find it in your transaction list.
- What does Internal Transactions mean?
- When a smart contract sends ETH to another address as part of its execution (not the original sender sending it), this shows as an internal transaction. For example, when you withdraw ETH from a DeFi protocol, the protocol contract sends ETH to you via an internal transaction. These are not separate user-initiated transactions but automated movements triggered by contract logic.
- Why does my transaction show 0 ETH value but tokens moved?
- ERC-20 token transfers show 0 ETH value because no ETH was sent. The token movement is handled by the token contract (calling its transfer function). Look at the Tokens Transferred section to see what actually moved. You paid gas in ETH (the transaction fee) but the value field only shows native ETH sent.