Definition and scope
How to Interpret XRPL Transaction Metadata addresses a distinct part of developer guides. Read affected ledger nodes, delivered amounts, balance changes, and the actual outcome.
Reliable XRPL applications do more than submit JSON. They choose appropriate server connections, manage pagination and subscriptions, construct and sign transactions safely, interpret tentative and validated results, and recover cleanly from interruption. Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
How it works
Validated metadata reports TransactionResult, delivered_amount where relevant, and AffectedNodes containing CreatedNode, ModifiedNode, and DeletedNode entries with before-and-after fields.
- AffectedNodes: verify this field, object, or component against the cited protocol documentation.
- CreatedNode: verify this field, object, or component against the cited protocol documentation.
- ModifiedNode: verify this field, object, or component against the cited protocol documentation.
- DeletedNode: verify this field, object, or component against the cited protocol documentation.
- TransactionResult: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A balance-change parser walks AffectedNodes, applies account and issuer perspectives correctly, and links each derived change to the transaction hash and validated ledger.
For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.
Open the related live demo or evidence lab →Limits, risks, and common confusion
Metadata describes ledger effects, not a human business interpretation. Partial payments, offer crossing, deleted nodes, and issued-currency sign conventions require protocol-specific handling.
Applications must preserve exact amounts, protect signing material, handle retries idempotently, and reconcile against validated ledgers.
Current network status
Network-independent guidance. This guide explains an operational or representational concept. Confirm live server values and service-specific behavior before relying on it in production.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.