Ethereum Receipt Status: Success Is Not a Transfer
Read Ethereum transaction receipt status correctly, distinguish execution success from token movement, and test failed and empty-log cases.
Read the guideIndexbase journal / ideas for builders
Blockchain data.
Worth understanding.
Practical guides to blockchain APIs, wallet data and the evidence behind a useful answer. Clear concepts, worked examples and better questions for your next integration.
Follow the article feed200 articles / page 4 of 13
Explore all guides
In-depth introductions and focused field guides, organised around practical questions.
Ethereum JSON-RPC Quantities and Hex Data
Decode Ethereum JSON-RPC quantities and byte strings without confusing hexadecimal values, token amounts, addresses or padded contract data.
Read the guideeth_call vs Sending an Ethereum Transaction
Compare eth_call with transaction submission, including state changes, simulation context, gas assumptions and the limits of a successful call.
Read the guideEthereum Transaction Nonces and Replacement Tracking
Learn how Ethereum account nonces order transactions, why replacement transactions share a nonce, and how to model pending and confirmed records.
Read the guideEthereum Calldata: Selectors, Arguments and Meaning
Understand Ethereum transaction input data, four-byte selectors and ABI arguments, including why decoding alone cannot prove a business action.
Read the guideEthereum Log Bloom Filters: Useful but Not Exact
Learn what Ethereum log bloom filters can and cannot establish, why false positives matter, and how to verify actual matching event logs.
Read the guideContract Creation Transactions and Deployed Addresses
Distinguish contract creation input, receipt contract addresses and factory deployments, so a deployment inventory does not miss internal creations.
Read the guideEthereum State Data vs Transaction History
Compare Ethereum state reads with transaction history, and learn why a present balance cannot reveal every transfer that produced it.
Read the guideChain ID vs Network ID in Ethereum Applications
Understand chain ID and network ID, prevent cross-network record collisions, and choose the correct identifier for API requests and storage keys.
Read the guideFinding an Ethereum Block Near a Timestamp
Find a block near a timestamp with an explicit boundary rule, then verify the result before using it for a historical snapshot or report.
Read the guidePending Ethereum Transactions: Observation vs Inclusion
Model pending Ethereum transactions without treating a mempool observation as confirmation, and handle replacement, disappearance and delayed receipts.
Read the guideBatch Ethereum JSON-RPC Requests Safely
Batch Ethereum JSON-RPC reads while matching responses by ID, handling individual errors and avoiding the assumption of one shared block snapshot.
Read the guide
Paginating Wallet History Without Missing Records
Build wallet-history pagination around stable ordering, explicit boundaries and deduplication so repeated requests do not lose or duplicate activity.
Read the guideIncoming, Outgoing and Self Token Transfers
Classify wallet transfer direction with sender and recipient comparisons, while handling self-transfers, fees and multiple movements in one transaction.
Read the guideNative Currency vs Token Transfers in Wallet Data
Separate native-currency movement from contract-token events, including execution fees and why one transaction can affect several different assets.
Read the guide
Token Decimals and Exact Amount Arithmetic
Convert token base units into display amounts using exact arithmetic, preserve raw integers, and avoid rounding errors in balances and reconciliation.
Read the guideThe editorial approach
Useful questions.
Traceable explanations.
Each guide starts with a concrete developer question and separates technical observations from the interpretation an application adds. Worked examples use illustrative values; references point to standards and technical documentation.
Published by Indexbase. Explore related guides as your requirements develop, from a first data question to a more deliberate integration workflow.