Simple
A transaction is a signed request to change XRP Ledger state. A submitted request is not final until it appears in a validated ledger with a successful result.
XRPL Transactions
Understand XRP Ledger transactions, inspect a validated transaction, decode its fields, and verify the final result from ledger metadata.
UNDERSTAND
Simple first. Technical when you need it.
Technical
Applications should preserve the transaction hash, inspect validated=true, read meta.TransactionResult, and use delivered_amount for payment outcomes. The initial submit response alone is not proof of settlement.
REAL EXAMPLE
The hash is the durable receipt
A validated Payment has a unique hash, fee, source account, destination, sequence, ledger index, and metadata. XRPAuthority's decoder asks a public server for that record and explains the fields without requesting a secret.
Read the finality specification ↗TRY IT
Test the concept safely.
Interactive experience
Use the existing XRPAuthority tool or learning workflow. Live tools request public data only; simulations never ask for signing material.
Decode a transaction hash →Evidence boundary
Keep the network, validated ledger, hash, result, exact asset identity, and retrieval time with any conclusion. A protocol capability does not prove a person, issuer, or service is trustworthy.
GO DEEPER
Guides, entities, and research paths.
- Original data opportunity: Transaction-result breakdown
- Original data opportunity: Fee history by transaction type
- Original data opportunity: Validated confirmation-time samples