Read Ethereum and Base history

Ethereum and Base use accounts and balances. Their transactions do not consume individually numbered Bitcoin-style outputs. To understand an account’s activity, you need to distinguish the transaction that initiated execution from the transfers and other effects produced during execution.

A concrete zero-value transaction

This Base transaction, 0xdeaaab4b79d2fedef1c0086ff46930fd038c14c9f1bb836d71a39168d8e97f41, was included in block 51,848,294. The saved provider observation reports successful execution, a native value of zero, 198,593 gas used, and an actual fee of 993,578,086,322 wei (0.000000993578086322 ETH).

Its input begins with 0xf78ac752. The provider did not decode that method into a name. These fields establish neither the contract’s purpose nor the identities of its users. Zero native value also does not establish that no tokens moved or that no internal contract calls occurred.

Inspect the saved transaction observation and its source manifest. The source is Blockscout’s transaction API.

Two views, two different questions

• Direct transactions: transactions where the selected address is the initiating sender or direct recipient. Failed transactions remain visible; their requested value must not be counted as a successful transfer.
• ERC-20 transfers: token transfer events involving the address, including transfers initiated by another account. The contract address identifies the token on that network. Its symbol and decimals are metadata, not a guarantee of authenticity.

An unsolicited token event can appear without the recipient choosing to interact. A token with a familiar symbol can be an unrelated contract. A recorded event alone is not proof of consent, a legitimate balance, or a transaction’s economic meaning.

Coverage stays visible

Each view loads at most 50 events per page. “End of results” means that the provider returned no continuation for that view. It is not an audit of the indexer, and it does not cover internal native-value movements, NFTs, approvals, bridge attribution, other networks, or off-chain activity. The transaction page currently saves provider transaction fields; it does not reconstruct a full execution trace or independently verify finality.

On Base, inclusion in an L2 block is not the same assertion as settlement finality on Ethereum. The history interface reports the provider’s inclusion observation without turning it into a stronger claim.

Save enough context to check later

Keep the network, contract address, transaction hash, event index, amount in base units, source, and observation time. ztrash’s Evidence download preserves the loaded pages. Live observations expire from the cache after seven days; the versioned evidence files attached to these explainers remain in the site.

For the underlying models, see Ethereum’s documentation on accounts and transactions, the ERC-20 specification, and Base’s finality documentation.

Edition 1 · September 26, 2026 (Pacific). These are explanations of public provider observations, not identity findings. Each evidence bundle records its UTC collection time and file hashes. Corrections should identify the transaction, disputed statement, and supporting source; use the Support link in the site footer. Material corrections will be recorded in a new edition while retaining this evidence bundle.