How to Read Etherscan: Understanding Ethereum Transactions

Etherscan is a block explorer — a website that reads and displays Ethereum's public blockchain data in human-readable form, letting anyone look up a transaction, address, or block without running their own node. Reading a transaction page correctly means understanding a handful of fields: the transaction hash, status, gas used, input data, and any internal transactions it triggered.

The transaction hash and status

Every Ethereum transaction has a unique identifying hash, a long string starting with "0x" that you can paste into Etherscan's search bar to pull up its details. At the top of the transaction page, the status field shows whether it succeeded, failed, or is still pending. A failed transaction still consumed gas (it was included in a block and executed partway before reverting) even though it didn't achieve its intended effect — an important distinction for anyone reconciling why they paid a fee for something that didn't go through.

From, to, and value

These three fields show the sending address, the receiving address (or the /glossary/smart-contract address being called), and the amount of ETH directly transferred in the transaction. Note that a value of zero doesn't necessarily mean nothing of value moved — many DeFi interactions send zero ETH directly but move tokens through the contract logic instead, which is reflected in a separate section further down the page.

Gas used, gas limit, and gas price

This section shows how much /glossary/gas the transaction actually consumed relative to the maximum it was allowed to use (the gas limit), along with the base fee and priority fee paid — the same distinction covered in /blog/what-is-gas-limit-vs-gas-price. Gas used close to the gas limit can indicate the transaction nearly ran out of gas, which is one common cause of failure. Comparing this against typical costs helps when estimating fees in advance, as discussed in /blog/how-to-estimate-ethereum-gas-fees.

Input data

The input data field shows the raw instructions sent to a contract — which function was called and what arguments were passed. Etherscan often decodes this automatically into a readable function name and parameter list when the contract's source code and /glossary/smart-contract interface have been verified and published. When input data reads as "0x" with nothing else, it typically means the transaction was a simple ETH transfer rather than a contract interaction.

Internal transactions (token transfers and traces)

Many transactions trigger further transfers of ETH or tokens as a side effect of contract execution — for example, a swap on a decentralized exchange (see /blog/dex-vs-cex) moves multiple tokens between contract addresses in a single outer transaction. These are shown separately as "internal transactions" or in a "Tokens Transferred" section, since they don't appear as their own top-level transactions on-chain but are still part of what actually happened.

Key fields at a glance

Field	What it tells you
Transaction hash	Unique identifier for looking up this specific transaction
Status	Whether the transaction succeeded, failed, or is pending
From / To	Sending address and receiving address or contract
Value	ETH transferred directly (not counting token transfers)
Gas used / limit	Actual gas consumed versus the maximum allowed
Input data	The function call and arguments sent to a contract
Internal transactions	Transfers triggered indirectly by the contract's execution

Verifying contract source code

When a contract's source code has been verified on Etherscan, you can read the actual Solidity (see /blog/what-is-solidity-programming-language) behind it under the "Contract" tab, rather than trusting only the compiled bytecode. This is a useful habit before interacting with an unfamiliar contract, since it lets you (or someone more technical) check what a function actually does before granting it any /glossary/wallet permissions — a precaution relevant to avoiding the risks covered in /blog/how-token-approvals-work-ethereum.

Reading an address page, not just a transaction

Beyond individual transactions, Etherscan lets you look up an entire address to see its full transaction history, current ETH and token balances, and — for contract addresses — whether the code has been verified and what functions it exposes. This is useful for checking an unfamiliar address before sending funds to it, or for reviewing your own wallet's complete activity history across every protocol you've ever interacted with, since a single address page aggregates all of it in one place rather than requiring you to remember every individual transaction.

Understanding transaction fees paid versus estimated

A completed transaction's page shows the actual transaction fee paid, calculated from gas used multiplied by the effective gas price at the time — a useful way to check after the fact whether your fee estimate, made using the approach covered in /blog/how-to-estimate-ethereum-gas-fees, was accurate. Comparing several of your own past transactions this way over time can help calibrate expectations for how much a similar future transaction is likely to cost under similar network conditions.

Using Etherscan for due diligence

Beyond individual transactions, Etherscan lets you check an address's full history, current token holdings, and whether a contract has been flagged for suspicious activity by the community — useful context before trusting an unfamiliar protocol, alongside the general precautions in /blog/common-defi-scams.

Bottom line

Reading an Etherscan transaction page comes down to a small set of fields: the hash identifies it, the status shows the outcome, gas fields show what was paid, and input data plus internal transactions reveal what actually happened under the hood. Getting comfortable with these basics turns raw blockchain data into something you can verify for yourself, rather than something you take on faith.