Ether scan
Ether scan searches connect Ethereum transaction outcomes with gas costs
Ether scan searches on Etherscan reveal Ethereum transaction status, execution costs, and the addresses involved in an operation. A transaction hash identifies the submitted transaction; its record shows whether it remains pending or has executed in a block. To establish whether a payment or contract action achieved its purpose, compare the execution status with the actual transfers and resulting contract state.
Last updated:
The explorer also provides address histories, token records, block information, and contract inspection tools. These views answer different questions: a transaction records one operation, while an address balance reflects the combined effects of activity over time.
Finding the transaction behind a wallet entry
A transaction hash from the sending wallet identifies the record to inspect, provided the explorer covers the network used for submission. Confirm the network before interpreting an absent result. An Ethereum mainnet search does not establish whether an operation exists on a different network.
The transaction record contains the sender, destination, status, and submitted data. For an included transaction, it also identifies the containing block and execution charge. Compare those fields with the original operation. The destination may be a contract handling the request, so the final asset recipient can appear in transfer details rather than the main destination field.
An address search provides another entry point when the hash is unavailable. Its history helps locate the relevant transaction by activity and time.
Does a successful transaction mean the payment is complete?
A successful transaction confirms successful execution at the transaction level; the intended payment still requires the correct asset movement to the correct recipient.
Execution status
An Ethereum transaction receipt records whether its top-level execution succeeded or failed. A successful approval changes spending permission, for instance, without completing the later operation requiring that permission. Read the called function and relevant transfers alongside the status. This distinguishes a completed request from a successfully completed prerequisite.
Confirmations and finality
Block inclusion, execution success, and finality describe different properties. Confirmations reflect subsequent blocks, while finality comes from Ethereum consensus. A receiving service may also apply its own deposit-crediting requirements. Consequently, a successful transaction and an unchanged service balance can coexist while that service processes the deposit.
A finalized failed transaction remains failed. Additional confirmations do not rerun its contract call or change the execution outcome.
Gas used and the final charge
The execution charge depends on the gas consumed and the effective price per gas when the transaction executes. Gas measures computational work; its price determines the ETH cost of that work.
The execution gas fee equals gas used multiplied by the effective gas price. When the price uses gwei, converting the result to ETH requires multiplying by 0.000000001. Keep units consistent when comparing a wallet estimate with the recorded fee.
The gas limit caps the gas available for execution. It is not a prediction of the final charge. For dynamic-fee transactions, the base fee and effective priority fee determine the execution price within the sender’s fee cap. Unused execution gas does not become an additional charge merely because the sender allowed a higher limit.
An included transaction still incurs gas charges when execution fails. A transaction rejected before inclusion does not incur that on-chain execution charge. The explorer’s gas tracker estimates conditions for upcoming transactions; it does not alter a recorded fee. Transaction types carrying blobs also have a separate blob fee, so the execution calculation alone does not describe every transaction’s total cost.
Why can a pending transaction disappear?
A pending transaction can disappear because nodes drop it from their transaction pools, or because another transaction replaces it. Neither condition means the original transaction successfully executed.
Dropped transactions can reappear if someone rebroadcasts them. A missing pending entry therefore does not establish permanent cancellation. Replacement involves another transaction from the same sender using the same nonce, the account’s transaction sequence number. When the replacement confirms, inspect its hash and contents: it may preserve the original operation or perform a different one.
A wallet’s cancellation attempt competes with the original pending transaction through replacement. It cannot reverse an already completed transfer. A dropped transaction that never executes incurs no on-chain execution fee, while an included replacement incurs its own charge.
Recognising an exhausted gas limit before retrying
Consider a hypothetical contract call whose receipt shows failure and whose explorer record identifies an out-of-gas error. The expected contract change is absent, although the sender paid an execution fee. The sender has retained the original hash and intended function arguments, so the failed attempt has a specific record to compare against a retry.
Inspecting that receipt and requesting a fresh gas estimate do not submit another transaction. In this case, the estimate indicates the operation needs more gas than the original limit allowed. The sender also checks the current contract state and intended arguments before signing. Increasing the price per gas alone would not correct an exhausted gas limit.
If estimation succeeds and the state and argument checks support the intended call, the sender submits the retry with an adequate gas limit. In this hypothetical case, the new receipt shows success and the expected contract change is present. Its new hash identifies the successful attempt; the original failed transaction and its charge remain in the history. If estimation instead reports a contract rejection, the sender stops before signing again and investigates that condition.
The gas limit bounds execution in both attempts. The amount of work the contract currently requires can change with its state.
Token balances and contract activity
Address and token views explain asset movement beyond the transaction’s headline fields. Contract calls can produce several transfers, making the associated records necessary for reconciliation.
Token records
A token contract address identifies the asset on the selected network more precisely than its displayed name or symbol. Token pages expose transfer activity and holder information. ERC-20 records describe fungible tokens; ERC-721 and ERC-1155 records include identifiers needed to distinguish relevant token holdings. For a particular operation, match the contract, recipient, and transferred quantity or token identifier, including both quantity and identifier for ERC-1155 transfers.
Internal activity
Internal transaction views show activity arising during contract execution, including contract-mediated ETH transfers. These entries belong to an enclosing transaction rather than separate transactions independently signed by the account. Their relationship to the original hash helps explain why a contract received the initial call while another address received ETH.
Event logs supply further detail about contract execution. Interpret them using the emitting contract’s behavior: a familiar event name alone does not establish asset authenticity.
Can reading a contract change its state?
Reading public contract data through a read-only call does not change blockchain state or require an on-chain gas payment. Contract pages can expose these calls alongside functions that submit transactions.
Writing to a contract requires authorization through a wallet and can change balances or permissions. Before signing, inspect the contract address, function, arguments, and any ETH attached to the call. An ERC-20 approval authorizes a specified spender up to an allowance; unused permission can remain after the immediate task ends.
Source-code verification establishes correspondence between published source code and deployed contract bytecode. Verification does not establish that a contract is safe or audited. Read-only inspection and verified code help explain an operation, but neither substitutes for understanding the transaction being authorized.
Keeping a usable transaction record
A useful record retains the network, transaction hash, relevant addresses, actual asset movement, and execution fee. Include any replacement hash so later reconciliation follows the transaction that executed. A current address balance can include unrelated activity, making it insufficient by itself to explain one payment.
Sharing a hash also exposes the public addresses and activity connected to that transaction. It does not reveal a private key, yet associating the record with a person can reveal financial activity. Private signing credentials have no role in transaction lookup.
The explorer presents blockchain records and cannot reverse transfers. Once the expected outcome is established, further action is necessary only if another condition remains outstanding, such as service crediting or an unused spending permission. Closing the browser does not remove that permission.
Frequently asked questions about Ether scan
Why does a token transfer show a value of 0 ETH?
The main value field measures native ETH attached to the transaction, not the quantity of tokens it moves. A token contract call can transfer tokens while attaching no ETH. Examine the token transfer details for the asset and amount, and read the transaction fee separately. A zero value field does not establish that the operation had no effect.
Can I export transaction history for a spreadsheet?
The explorer provides CSV downloads for transaction history and supported listing views. The exported data reflects the selected view and its coverage, so a download of ordinary transactions may not include every token transfer or internal entry needed for reconciliation. Retain transaction hashes in the spreadsheet to connect related records without counting the same operation twice.
Does adding a private address label change the blockchain record?
A private address label changes how the explorer presents an address within your signed-in account. It does not rename the address on the blockchain or change transaction contents. Private notes can help identify records later, while public labels follow a separate system. A label you assign also does not prove who controls the address.
Is disconnecting a wallet enough to revoke a token approval?
Disconnecting a wallet does not revoke an existing on-chain token allowance. The approval belongs to the token contract’s state and can remain usable by the approved spender. Revocation requires a transaction changing that permission, with the associated network fee. It affects future spending authority and does not recover tokens the spender has already transferred.
Where does the transaction fee go?
For an Ethereum dynamic-fee transaction, the protocol burns the execution base fee and the block’s fee recipient receives the priority fee. The explorer displays these amounts rather than collecting them as a search charge. These fee components pay for processing the transaction; they remain separate from any ETH value or tokens transferred by the operation.