Ethereum records combine account state with the results of contract execution. A transaction can move tokens even when its native ETH value is zero, and a failed call can still consume gas. Begin with the request, receipt, and relevant asset events to understand what actually changed for the accounts you track.
An Ethereum transaction requests a change to network state. Its fields describe the submitting address, destination, attached ETH value, and any encoded contract instructions. The destination can be a contract, so it is not always the final recipient of the tokens involved.
The official transaction documentation introduces these fields and the transaction lifecycle. For a ledger, pair that request with its execution receipt. A receipt supplies the outcome, block information, gas usage, and event logs needed to distinguish an intended action from a completed one.
Keep the chain and token contract address alongside any familiar symbol. When a contract emits several events, retain the transaction hash and event index so each movement remains identifiable. A single transaction can affect more than one asset or account.
Native ETH value and token quantity belong in separate fields. A zero ETH value can accompany a substantial token transfer, while the transaction's gas charge reduces a native balance. Record actual fee evidence rather than treating the configured gas limit as the amount consumed.
Check execution status first. If execution failed, do not classify the requested token action as complete merely because the transaction entered a block. Then inspect relevant events and identify the accounts they affect. Match the decoded quantities to the token's decimal convention.
Compare the resulting movements with balances observed at a consistent block boundary. Current balances may include later activity, so they cannot automatically describe the moment a historical transaction executed. Keep any unexplained difference as an open review item.
The Ethereum transaction and gas guide supplies a worked example and receipt checklist. For unusual metadata or multiple contracts sharing a ticker, continue with token identity and ledger records.
A successful receipt shows that execution completed under the network's rules. It does not establish that the contract was the one intended or that a displayed token has value. An explorer's short description is an interpretation that may need checking against the underlying records.
Permissions deserve separate attention because an approval can affect future actions without immediately moving tokens. The Web3 permission overview explains how to keep continuing authority visible alongside the transaction history.
The value field records native ETH attached to the transaction. Token movements are handled through contract execution and can appear in event logs. Read those events and the receipt before concluding that no assets moved.
Keep the failed attempt and any actual charge it incurred. A transaction can consume gas before reverting its intended execution changes, so the token movement and the fee need different treatment.
An approval changes an allowance under a token contract. It can authorize a spender to act later without moving tokens immediately. Record the permission separately and use transfer evidence to identify completed asset movements.
An Ethereum transaction can move tokens, update permissions, and charge an ETH fee. Learn to separate the original request from its receipt, interpret token events, and record contract activity without confusing displayed value with the assets actually moved.
Read the guide
Bitcoin records spendable outputs rather than a running balance for each person. Follow a worked payment example, identify change and fees, and learn how confirmations, wallet scope, and transaction identifiers affect a dependable record of activity.
Read the guide
Solana token activity often involves several accounts inside one transaction. Learn how wallet authorities, mint addresses, token accounts, instructions, and fee payments fit together, then use a practical example to build records that explain the actual balance changes.
Read the guide