# Stellar | Bitquery Data Store The whole Stellar network as flat Parquet: ledgers, transactions, operations, payments, transfers, effects, DEX trades, claimable balances and liquidity pools. Dataset page: https://bitquery.io/datastore/datasets/stellar Network: Stellar Category: Transactions, Transfers, Trades, Balances Tables: 12 Columns: 326 Coverage: first block to 2026-09-27 Format: Apache Parquet, ZSTD compression, one prefix per table Licence: https://bitquery.io/datastore/legal/data-license ## What this is Every indexed Stellar topic, as twelve flat Parquet tables at ledger resolution: blocks, transactions, operations, payments, transfers, effects, effect arguments, balance effects, trade effects, claimable balance effects, liquidity pool effects and liquidity pool trade effects. Stellar models activity in three layers — a transaction contains operations, and each operation emits effects. The schema keeps all three, so you can work at whichever level your question needs and join between them on tx_hash, operation_index and effect_index. ## What people use it for - Cross-border and remittance payment flow analysis, including multi-hop path payments - Anchor and issued-asset tracking across issuers and trustlines - Stellar DEX and AMM research: order-book trades and liquidity-pool swaps side by side - Compliance and forensics on a network built for regulated money movement ## Tables (12) ### blocks: 10 columns One row per Stellar ledger, with protocol version, fee pool and total coin supply. S3 prefix: stellar/blocks File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/blocks/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | hash | String | Ledger hash, hex | | block | UInt64 | Ledger sequence number | | max_tx_set_size | UInt64 | Maximum transactions the ledger could contain | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | protocol_version | UInt64 | Stellar protocol version in force at this ledger | | base_reserve | String | Base reserve as a rational string, numerator/denominator | | base_fee | String | Base fee as a rational string, numerator/denominator | | fee_pool | String | Accumulated fee pool as a rational string | | total_coins | String | Total XLM in existence at this ledger, as a rational string | ### transactions: 18 columns One row per Stellar transaction, with fee account, memo, operation count and success. S3 prefix: stellar/transactions File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/transactions/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | block | UInt64 | Ledger sequence number | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | fee_account | String | Account that paid the fee, which may differ from the sender on a fee-bump transaction | | fee_account_annotation | String | Bitquery label for the fee account, empty when unlabelled | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_hash_bin | String | Binary form of the transaction hash | | memo_type | String | Memo type: none, text, id, hash or return | | tx_index | UInt64 | Position of the transaction within the ledger | | memos | String | Memo contents, commonly a customer identifier at an exchange | | operation_count | UInt64 | Number of operations in the transaction | | sender | String | Source account of the transaction | | sender_annotation | String | Bitquery label for the sender, empty when unlabelled | | sequence | Int64 | Source account sequence number | | success | UInt8 | 1 when the transaction succeeded. Filter on this to exclude failures | | time_bounds | String | Validity window as an interval, for example [0,1735700082) | | timestamp_unixtime | Int64 | Ledger close time, Unix epoch seconds | | fee | String | Fee charged as a rational string, numerator/denominator | | max_fee | String | Maximum fee the sender authorised, as a rational string | ### operations_tx: 13 columns One row per operation, with its type and a JSON details blob carrying the type-specific fields. S3 prefix: stellar/operations_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/operations_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | block | UInt64 | Ledger sequence number | | details | String | JSON-encoded operation detail, whose keys vary by operation type | | op_index | UInt64 | Index of the operation within the ledger | | source_account | String | Account the operation runs as, which may differ from the transaction sender | | source_account_annotation | String | Bitquery label for the source account | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | transaction_sender | String | Source account of the parent transaction | | tx_hash_bin | String | Binary form of the transaction hash | | tx_index_raw | UInt64 | Position of the parent transaction within the ledger | | tx_sender_raw | String | Source account of the parent transaction, as recorded | | transaction_index | UInt64 | Normalised transaction index | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | operation | String | Operation type, for example payment, manage_buy_offer, create_claimable_balance | ### payments_tx: 46 columns One row per payment operation, including path payments, with both currency sides, issuers and the full conversion path. S3 prefix: stellar/payments_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/payments_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | block | UInt64 | Ledger sequence number | | currency_from_address | String | Source currency address; '-' for Stellar assets | | source_currency_id | UInt64 | Internal id of the source currency | | currency_from_name | String | Source currency name; 'Lumen' for native XLM, otherwise code plus issuer | | currency_from_symbol | String | Source currency symbol | | currency_from_tokenType | String | Source asset type: credit_alphanum4, credit_alphanum12, or '-' for native | | currency_from_tokenId | String | Source token identifier, when applicable | | currency_from_decimals | UInt64 | Decimals of the source currency; 7 on Stellar | | currency_to_address | String | Destination currency address | | currency_id | UInt64 | Internal id of the destination currency | | currency_to_name | String | Destination currency name | | currency_to_symbol | String | Destination currency symbol | | currency_to_tokenType | String | Destination asset type | | currency_to_decimals | UInt64 | Decimals of the destination currency | | currency_to_tokenId | String | Destination token identifier, when applicable | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | issuer_from | String | Issuer of the source asset, empty for native XLM | | issuer_from_annotation | String | Bitquery label for the source issuer | | issuer_to | String | Issuer of the destination asset, empty for native XLM | | issuer_to_annotation | String | Bitquery label for the destination issuer | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type: payment, path_payment_strict_send or path_payment_strict_receive | | op_source_account | String | Account the operation runs as | | operation_name | String | Operation name, same vocabulary as operation | | op_source_address | String | Address form of the operation source account | | op_source_annotation | String | Bitquery label for the operation source | | path | String | Conversion path for a path payment. Ruby hash-inspect format using =>, NOT valid JSON | | receiver | String | Destination account | | receiver_annotation | String | Bitquery label for the receiver | | sender | String | Paying account | | sender_annotation | String | Bitquery label for the sender | | success | UInt8 | 1 when this payment operation succeeded. A transaction can succeed while a path payment inside it fails | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_hash_bin | String | Binary form of the transaction hash | | tx_index_raw | UInt64 | Position of the transaction within the ledger | | tx_sender_raw | String | Source account of the parent transaction, as recorded | | transaction_index | UInt64 | Normalised transaction index | | transaction_sender | String | Source account of the parent transaction | | amount_to | String | Amount received, rational string numerator/denominator | | amount_from | String | Amount sent, rational string numerator/denominator | | credited_to_value | String | Value credited to the receiver, rational string | | debited_from_value | String | Value debited from the sender, rational string | | max_value_from | String | Sender's maximum on a strict-receive path payment, rational string | | min_value_to | String | Receiver's minimum on a strict-send path payment, rational string | ### transfers_tx: 30 columns One row per value movement with both currency sides, classified by direction. Amounts here are floats, unlike most other tables. S3 prefix: stellar/transfers_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/transfers_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_hash_bin | String | Binary form of the transaction hash | | tx_index_raw | UInt64 | Position of the transaction within the ledger | | tx_sender_raw | String | Source account of the parent transaction, as recorded | | transaction_sender | String | Source account of the parent transaction | | transaction_index | UInt64 | Normalised transaction index | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | sender | String | Account value moved from | | sender_annotation | String | Bitquery label for the sender | | receiver | String | Account or object value moved to; a claimable balance id on claimable_balance rows | | receiver_annotation | String | Bitquery label for the receiver | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type that produced the movement | | operation_name | String | Operation name, same vocabulary as operation | | direction | String | Row classification, for example payment or claimable_balance. Filter on this before aggregating | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | currency_to_name | String | Destination currency name, code plus issuer for issued assets | | currency_to_id | UInt64 | Internal id of the destination currency | | currency_to_address | String | Destination currency address; '-' for Stellar assets | | currency_to_tokenId | String | Destination token identifier, when applicable | | currency_to_tokenType | String | Destination asset type | | currency_from_address | String | Source currency address | | currency_from_id | UInt64 | Internal id of the source currency | | currency_from_name | String | Source currency name | | currency_from_tokenType | String | Source asset type | | currency_from_tokenId | String | Source token identifier, when applicable | | block | UInt64 | Ledger sequence number | | amount_to | Float64 | Amount arriving, as a FLOAT in asset units — not a rational string | | amount_from | Float64 | Amount leaving, as a FLOAT in asset units — not a rational string | ### effects_tx: 20 columns One row per effect, the ledger-level consequence of an operation, with a JSON details blob. S3 prefix: stellar/effects_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/effects_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | address | String | Account the effect applies to | | address_annotation | String | Bitquery label for that account | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | block | UInt64 | Ledger sequence number | | details | String | JSON-encoded effect detail, whose keys vary by effect type | | effect | String | Effect type, for example trade, account_credited, trustline_created | | effect_index | UInt64 | Index of the effect within its operation | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type that produced the effect | | op_source_account | String | Account the operation runs as | | operation_name | String | Operation name, same vocabulary as operation | | op_source_address | String | Address form of the operation source account | | op_source_annotation | String | Bitquery label for the operation source | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_index | UInt64 | Position of the transaction within the ledger | | tx_sender | String | Source account of the parent transaction | | transaction_index | UInt64 | Normalised transaction index | | transaction_sender | String | Source account of the parent transaction | | tx_time | Int64 | Ledger close time, Unix epoch seconds | ### effect_arguments_tx: 21 columns Effects flattened to one row per named argument, for querying effect fields without parsing JSON. S3 prefix: stellar/effect_arguments_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/effect_arguments_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | address | String | Account the effect applies to | | address_annotation | String | Bitquery label for that account | | argname | String | Name of the effect argument, for example amount or asset_code | | block | UInt64 | Ledger sequence number | | argvalue | String | Value of the argument, always as a string | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | effect | String | Effect type the argument belongs to | | effect_index | UInt64 | Index of the effect within its operation | | operation_index | UInt64 | Index of the operation within the transaction | | operation | String | Operation type that produced the effect | | op_source_account | String | Account the operation runs as | | op_source_annotation | String | Bitquery label for the operation source | | op_source_address | String | Address form of the operation source account | | operation_name | String | Operation name, same vocabulary as operation | | order | UInt64 | Sequence of the argument within the effect | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | transaction_sender | String | Source account of the parent transaction | | tx_index | UInt64 | Position of the transaction within the ledger | | tx_sender | String | Source account of the parent transaction | | transaction_index | UInt64 | Normalised transaction index | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | ### balance_effects_tx: 25 columns One row per balance change, with the currency and issuer. Amount here is raw stroops, unlike most other tables. S3 prefix: stellar/balance_effects_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/balance_effects_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | address | String | Account whose balance changed | | address_annotation | String | Bitquery label for that account | | block | UInt64 | Ledger sequence number | | currency_address | String | Currency address; '-' for Stellar assets | | currency_id | UInt64 | Internal currency id | | currency_decimals | UInt64 | Decimals of the currency; 7 on Stellar | | currency_name | String | Currency name; 'Lumen' for native XLM | | currency_properties | String | Extra currency properties, when present | | currency_symbol | String | Currency symbol | | currency_tokenId | String | Token identifier, when applicable | | currency_tokenType | String | Asset type: credit_alphanum4, credit_alphanum12, or '-' for native | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | effect_index | UInt64 | Index of the effect within its operation | | issuer | String | Issuing account, empty for native XLM | | issuer_annotation | String | Bitquery label for the issuer | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type that caused the change | | op_source_account | String | Account the operation runs as | | op_source_annotation | String | Bitquery label for the operation source | | order | UInt64 | Sequence of the effect within the ledger | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_index | UInt64 | Position of the transaction within the ledger | | tx_sender | String | Source account of the parent transaction | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | amount | String | Balance change in RAW STROOPS as an integer string; divide by 10,000,000. Not a rational string | ### trade_effects_tx: 41 columns One row per order-book trade on the Stellar DEX, with both sides, issuers, the offer id and the execution price. S3 prefix: stellar/trade_effects_tx File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/trade_effects_tx/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | address | String | Account the trade effect applies to | | address_annotation | String | Bitquery label for that account | | block | UInt64 | Ledger sequence number | | buy_currency_address | String | Bought currency address; '-' for Stellar assets | | buy_currency_id | UInt64 | Internal id of the bought currency | | buy_currency_decimals | UInt64 | Decimals of the bought currency | | buy_currency_name | String | Bought currency name, code plus issuer for issued assets | | buy_currency_symbol | String | Bought currency symbol | | buy_currency_tokenId | String | Bought token identifier, when applicable | | buy_currency_tokenType | String | Bought asset type | | buy_issuer | String | Issuer of the bought asset | | buy_issuer_annotation | String | Bitquery label for the bought asset issuer | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | effect_index | UInt64 | Index of the effect within its operation | | offer_id | Int64 | Identifier of the order-book offer that was filled | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type that produced the trade | | op_source_account | String | Account the operation runs as | | operation_name | String | Operation name, same vocabulary as operation | | op_source_address | String | Address form of the operation source account | | order | UInt64 | Sequence of the effect within the ledger | | sell_currency_name | String | Sold currency name, code plus issuer for issued assets | | sell_currency_id | UInt64 | Internal id of the sold currency | | sell_currency_symbol | String | Sold currency symbol | | sell_currency_tokenId | String | Sold token identifier, when applicable | | sell_currency_tokenType | String | Sold asset type | | sell_currency_address | String | Sold currency address | | sell_currency_decimals | UInt64 | Decimals of the sold currency | | sell_issuer | String | Issuer of the sold asset | | seller | String | Counterparty account on the sell side | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_hash_bin | String | Binary form of the transaction hash | | tx_index_raw | UInt64 | Position of the transaction within the ledger | | tx_sender_raw | String | Source account of the parent transaction, as recorded | | transaction_index | UInt64 | Normalised transaction index | | transaction_sender | String | Source account of the parent transaction | | buy_amount | String | Amount bought, rational string numerator/denominator | | price_amount | String | Execution price, rational string; the denominator can be 1 | | sell_amount | String | Amount sold, rational string numerator/denominator | ### claimable_balance_effects: 28 columns One row per claimable balance effect, with the balance id, sponsor, claimant and amount. S3 prefix: stellar/claimable_balance_effects File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/claimable_balance_effects/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | block | UInt64 | Ledger sequence number | | balance_id | String | Claimable balance identifier, hex | | claimant | String | Account entitled to claim, empty on the creation effect | | claimant_annotation | String | Bitquery label for the claimant | | currency_address | String | Currency address; '-' for Stellar assets | | currency_id | UInt64 | Internal currency id | | currency_decimals | UInt64 | Decimals of the currency | | currency_name | String | Currency name, code plus issuer for issued assets | | currency_properties | String | Extra currency properties, when present | | currency_symbol | String | Currency symbol | | currency_tokenId | String | Token identifier, when applicable | | currency_tokenType | String | Asset type | | effect | String | Effect type, for example claimable_balance_created_effect_response | | effect_index | UInt64 | Index of the effect within its operation | | issuer | String | Issuing account of the asset | | issuer_annotation | String | Bitquery label for the issuer | | operation_index | UInt64 | Index of the operation within the transaction | | operation | String | Operation type, for example create_claimable_balance or claim_claimable_balance | | op_source_account | String | Account the operation runs as | | op_source_annotation | String | Bitquery label for the operation source | | order | UInt64 | Sequence of the effect within the ledger | | sponsor | String | Account sponsoring the reserve for the claimable balance | | sponsor_annotation | String | Bitquery label for the sponsor | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_index | UInt64 | Position of the transaction within the ledger | | tx_sender | String | Source account of the parent transaction | | amount | String | Amount held or claimed, rational string numerator/denominator | ### liquidity_pool_effects: 31 columns One row per liquidity pool deposit or withdrawal, with the pool's full reserve state at the time. S3 prefix: stellar/liquidity_pool_effects File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/liquidity_pool_effects/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | block | UInt64 | Ledger sequence number | | currency_address | String | Currency address; '-' for Stellar assets | | currency_id | UInt64 | Internal currency id | | currency_decimals | UInt64 | Decimals of the currency | | currency_name | String | Currency name, code plus issuer for issued assets | | currency_properties | String | Extra currency properties, when present | | currency_symbol | String | Currency symbol | | currency_tokenId | String | Token identifier, when applicable | | currency_tokenType | String | Asset type | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | effect_index | UInt64 | Index of the effect within its operation | | effect | String | Effect type, for example liquidity_pool_deposited_effect_response | | issuer | String | Issuing account of the asset | | liquidity_pool_details | String | JSON-encoded pool state: id, type, fee_bp, reserves, total_shares, total_trustlines | | liquidity_pool_id | String | Liquidity pool identifier, hex | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type: liquidity_pool_deposit or liquidity_pool_withdraw | | op_source_account | String | Account the operation runs as | | operation_name | String | Operation name, same vocabulary as operation | | op_source_address | String | Address form of the operation source account | | op_source_annotation | String | Bitquery label for the operation source | | order | UInt64 | Sequence of the effect within the ledger | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_index | UInt64 | Position of the transaction within the ledger | | tx_sender | String | Source account of the parent transaction | | transaction_index | UInt64 | Normalised transaction index | | transaction_sender | String | Source account of the parent transaction | | amount | String | Amount deposited or withdrawn, rational string numerator/denominator | | shares | Float64 | Pool shares minted or burned by the operation | ### liquidity_pool_trade_effects: 43 columns One row per AMM swap against a Stellar liquidity pool, with both sides and the pool's reserve state at the time. S3 prefix: stellar/liquidity_pool_trade_effects File naming: _.parquet, 50 ledgers per file Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/stellar/liquidity_pool_trade_effects/55080300_55080349.parquet | column | type | description | | --- | --- | --- | | transaction_sender | String | Source account of the parent transaction | | tx_hash_bin | String | Binary form of the transaction hash | | tx_index_raw | UInt64 | Position of the transaction within the ledger | | tx_sender_raw | String | Source account of the parent transaction, as recorded | | transaction_index | UInt64 | Normalised transaction index | | tx_hash | String | Transaction hash, hex. Join key across every stellar table | | tx_time | Int64 | Ledger close time, Unix epoch seconds | | sell_issuer | String | Issuer of the sold asset | | sell_issuer_annotation | String | Bitquery label for the sold asset issuer | | sell_currency_address | String | Sold currency address; '-' for Stellar assets | | sell_currency_id | UInt64 | Internal id of the sold currency | | sell_currency_decimals | UInt64 | Decimals of the sold currency | | sell_currency_name | String | Sold currency name, code plus issuer | | sell_currency_properties | String | Extra properties of the sold currency | | sell_currency_symbol | String | Sold currency symbol | | sell_currency_tokenId | String | Sold token identifier, when applicable | | sell_currency_tokenType | String | Sold asset type | | order | UInt64 | Sequence of the effect within the ledger | | operation_index | UInt64 | Index of the operation within the transaction | | op_index | UInt64 | Index of the operation within the ledger | | operation | String | Operation type that produced the swap, for example path_payment_strict_receive | | op_source_account | String | Account the operation runs as | | operation_name | String | Operation name, same vocabulary as operation | | op_source_address | String | Address form of the operation source account | | op_source_annotation | String | Bitquery label for the operation source | | liquidity_pool_id | String | Liquidity pool identifier, hex | | liquidity_pool_details | String | JSON-encoded pool state at the time of the swap, including reserves and fee_bp | | effect_index | UInt64 | Index of the effect within its operation | | tx_date | Int64 | UTC date of the ledger, Unix epoch milliseconds | | buy_issuer | String | Issuer of the bought asset | | buy_issuer_annotation | String | Bitquery label for the bought asset issuer | | buy_currency_address | String | Bought currency address | | buy_currency_id | UInt64 | Internal id of the bought currency | | buy_currency_name | String | Bought currency name, code plus issuer | | buy_currency_decimals | UInt64 | Decimals of the bought currency | | buy_currency_symbol | String | Bought currency symbol | | buy_currency_tokenType | String | Bought asset type | | buy_currency_tokenId | String | Bought token identifier, when applicable | | address | String | Account the swap effect applies to | | address_annotation | String | Bitquery label for that account | | block | UInt64 | Ledger sequence number | | sell_amount | String | Amount sold into the pool, rational string numerator/denominator | | buy_amount | String | Amount bought from the pool, rational string numerator/denominator | ## Price - Latest month (Aug 27, 2026 → Sep 27, 2026): $600 one-time, USD - Last 12 months (Sep 27, 2025 → Sep 27, 2026): $6,000 one-time, USD - Last 24 months (Sep 27, 2024 → Sep 27, 2026): $8,000 one-time, USD - Full history (Genesis → Sep 27, 2026): $10,000 one-time, USD Every window includes all 12 tables and 326 columns. Only the time range changes. ## Questions buyers ask Q: What is included in the Stellar dataset? A: Twelve Parquet tables with 326 documented columns in total: blocks, transactions, operations_tx, payments_tx, transfers_tx, effects_tx, effect_arguments_tx, balance_effects_tx, trade_effects_tx, claimable_balance_effects, liquidity_pool_effects and liquidity_pool_trade_effects. Covering the most recent month to yesterday, refreshed daily. Q: Why are amounts written as 29377351/10000000? A: Most amount columns are exact rational strings: numerator, slash, denominator. Stellar uses 7 decimal places, so the denominator is normally 10000000 and the value above is 2.9377351 XLM. Parse and divide rather than casting the string to a float. Keeping the fraction means no precision is lost at export. Q: Are all amounts in that format? A: No, and this is the trap worth knowing before you aggregate. Three representations appear: rational strings in payments_tx, trade_effects_tx, claimable_balance_effects, the liquidity pool tables, and the fee and reserve columns of blocks and transactions; plain floats in transfers_tx (amount_from, amount_to); and raw stroops as an integer string in balance_effects_tx (amount), where 7481895 means 0.7481895. Check the table before summing, and never add columns across tables without converting first. Q: Does the data include failed transactions and operations? A: Yes. transactions carries success, and payments_tx carries its own success flag at operation level — a transaction can succeed while an individual path payment fails. Filter success = 1 on whichever table you are aggregating. Q: How do the three layers fit together? A: A transaction holds one or more operations, and each operation emits zero or more effects. Join transactions to operations_tx on tx_hash, and operations to the effect tables on tx_hash plus operation_index. effect_index orders effects within an operation, and order gives their sequence within the ledger. Q: What format are the details, path and liquidity_pool_details columns? A: details and liquidity_pool_details are JSON-encoded strings you can parse directly. The path column in payments_tx is NOT JSON: it is Ruby hash-inspect format using => instead of a colon, for example [{"asset_code"=>"YBX"}]. A standard JSON parser will reject it — convert => to : first, or parse it with a permissive reader. Q: What are the _annotation columns? A: Bitquery address labels for the account in the adjacent column — an exchange or anchor name where we have one. They are frequently empty, so treat them as a bonus for entity resolution rather than a field you can rely on being populated. Q: Does this cover the Stellar DEX and AMMs separately? A: Yes, and they are distinct tables because they are distinct mechanisms. trade_effects_tx holds order-book trades with an offer_id, while liquidity_pool_trade_effects holds AMM swaps with a liquidity_pool_id and the pool's reserves at the time. liquidity_pool_effects covers deposits and withdrawals rather than swaps. Q: How is the data delivered? A: As flat Parquet files under a stable S3 layout, one prefix per table, with a JSON manifest listing every file and its sha256. Signed HTTPS links are emailed to you once the files are prepared. Q: How current is the data? A: Refreshed daily with T+1 latency. A purchase made today includes everything up to yesterday. Q: Can I try before I buy? A: Yes. Every table links to a public sample file with real records, and the sample bucket holds full Parquet files you can load directly. No email address required. ## What this file is, and is not This is a description of one dataset sold by Bitquery, written for assistants and for people. It lists every column but holds no data rows. The sample files linked under each table are real Parquet and are free to download. Figures here come from the product record and are exact unless marked otherwise; the delivery manifest is authoritative for a purchased file. If a question needs a row that is not in a sample, say so rather than guessing at it.