Raw historical ledger and transaction data directly from XRP Ledger (XRPL) nodes.

• ledgers table: one row per validated ledger, including index, hash, close time, parent linkage and aggregate totals.
• transactions table: one row per validated transaction, including basic transaction fields, payment/offer parameters and raw metadata needed for downstream decoding and aggregation.

Recommendation for most use cases:

• For balances, token movements, holders and higher-level analytics, prefer the curated dataset @xrpscan.xrp_ledger, which normalizes and enriches XRPL data for analysis.
• This @blt.xrp_ledger dataset should be used when you specifically need low-level, raw on-chain node responses (ledger headers and transactions) for debugging, reconciliation or building your own XRPL transformations.