Definition and scope
Ledger Indexes, Hashes, and Close Times Explained addresses a distinct part of xrp and ledger fundamentals. Identify a ledger version by its sequence, cryptographic hash, and recorded close time.
This collection establishes the language needed to evaluate every other XRP Ledger topic. It separates the asset from the network, explains the identifiers visible in explorers, and shows how individual transactions fit into an ordered ledger history. Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.
How it works
The ledger index is a sequence number, the ledger hash identifies exact contents, and close time records the consensus-estimated time. Together they let systems refer to a particular validated state without treating timestamps as unique identifiers.
- ledger_index: verify this field, object, or component against the cited protocol documentation.
- ledger_hash: verify this field, object, or component against the cited protocol documentation.
- parent_hash: verify this field, object, or component against the cited protocol documentation.
- close_time: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
A reconciler can store ledger_index and ledger_hash with a transaction result, then confirm that a later server reports the same validated ledger before crediting a customer.
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
Close time is rounded and consensus-derived, not a precision wall clock. An index alone can be ambiguous across separate networks, so operational records should also retain network and hash context.
Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.
Current network status
Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.