Skip to main content
stellar holds the standardized Stellar tables. Stellar calls its blocks ledgers, and they land in blocks. A transaction here is a wrapper: what it does is carried in a list of operations. So transactions land in transactions, the operations inside them in operations, and what each operation changed in effects.

Tables

TableSinceDescription
blocks2015-09One row per ledger, with transaction counts, fee pool and total lumens.
transactions2015-09One row per transaction, with its fees, the account that sent it, and the original encoded form.
operations2015-09One row per operation, typed by operation_type.
effects2015-09One row per state change an operation produced.
Ledgers are keyed on number, transactions on transaction_hash, operations on operation_id and effects on effect_id. The tables get finer as you go down: a transaction holds one or more operations, and an operation produces any number of effects, including none. For payments and trades, start from operations and filter on operation_type. Use effects when the question is who was credited and who was debited.

Sample queries

Count operations by type on one day.

Notes

Above the raw tables sits the rest of the catalog, and Stellar shows up in two parts of it: the tokenized assets issued on it, and the list of tokens we know about with the daily prices they carry. Tokenized funds and stablecoins make up most of the asset side. No app or trading-pool table covers the chain. The market pages go deeper on each of these. Tokenized assets and Stablecoins cover the tokenized assets and their daily tables. Tokens covers the token list and the daily price table.