ripple holds the standardized XRP Ledger tables. The XRP Ledger calls its blocks ledgers, and they land in blocks. Transactions land in transactions, which is wide: it has a column for every field any kind of transaction can hold, and only the ones that apply to that kind are filled in. Everything a transaction changed lands in affected_nodes.
Above the raw tables sits the rest of the catalog, and the XRP Ledger shows up in two parts of it: the tokenized assets issued on it, and the list of tokens we know about with their daily prices. Tokenized funds, stablecoins and tokenized commodities make up the asset side.
The market pages go deeper on each of these. Stablecoins and Real-world assets cover the tokenized assets and their daily tables. Tokens covers the token list and the daily price table.
Tables
| Table | Since | Description |
|---|---|---|
blocks | 2013-01 | One row per ledger, with close times and total XRP in existence. |
transactions | 2013-01 | One row per transaction, with the columns its transaction_type populates. |
affected_nodes | 2013-01 | One row per ledger entry a transaction created, modified or deleted. |
number and transactions on transaction_hash. Each affected_nodes row has new_fields, final_fields and previous_fields as JSON, so you can see what a record held before the change and after it.
The columns that hold amounts, amount, deliver_max and delivered_amount, are JSON rather than numbers. An amount on this chain is one of two things: a plain count of drops if it is XRP, one drop being a millionth of an XRP, or a small record naming the currency, its issuer and the value if it is anything else. For payments, read delivered_amount: it says what arrived, which is not always what was asked for, because the chain allows a payment to deliver less than its stated amount.
Sample queries
- Transaction success rate
- Tokenized assets ranked
- Priced tokens
Count transactions by type and their success rate on one day.
tesSUCCESS is the result code of a successful transaction.