blocks
14 columnsOne row per block: size, weight, difficulty, chainwork and transaction count.
litecoin/blocks<start_block>_<end_block>.parquetone file per block rangeThe full Litecoin ledger since October 2011: blocks, transactions, inputs and outputs with LTC, litoshi and USD values at block time.
Every Litecoin block, transaction, input and output from the genesis block in October 2011 to yesterday, with values in LTC, litoshi and USD at block time. Addresses and script types are decoded on every input and output, and each output carries a change heuristic.
Inputs carry the hash and index of the output they spend, so UTXO traversal and coin-age calculations are a single join rather than a replay. Files are cut by block range and named by their first and last block, so any window can be assembled exactly.
One row per block: size, weight, difficulty, chainwork and transaction count.
litecoin/blocks<start_block>_<end_block>.parquetone file per block rangeOne row per transaction with input, output, fee and mined values in LTC, litoshi and USD.
litecoin/transactions<start_block>_<end_block>.parquetone file per block rangeOne row per transaction input, referencing the output it spends, with address, script type and value.
litecoin/inputs<start_block>_<end_block>.parquetone file per block rangeOne row per transaction output with address, script type, change heuristic and value.
litecoin/outputs<start_block>_<end_block>.parquetone file per block rangeblocks14 columnsOne row per block: size, weight, difficulty, chainwork and transaction count.transactions25 columnsOne row per transaction with input, output, fee and mined values in LTC, litoshi and USD.inputs17 columnsOne row per transaction input, referencing the output it spends, with address, script type and value.outputs18 columnsOne row per transaction output with address, script type, change heuristic and value.Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# blocks: one file per block range litecoin/blocks<start_block>_<end_block>.parquet # transactions: one file per block range litecoin/transactions<start_block>_<end_block>.parquet # inputs: one file per block range litecoin/inputs<start_block>_<end_block>.parquet # outputs: one file per block range litecoin/outputs<start_block>_<end_block>.parquet
Four Parquet tables: blocks, transactions, inputs and outputs, covering full history from the genesis block to yesterday. Every input and output carries its address, script type and value in LTC, litoshi and USD.
MWEB extension-block transfers are confidential by design, so their amounts and addresses are not on the main chain. The peg-in and peg-out transactions that move coins to and from MWEB appear as ordinary inputs and outputs, with the witness_mweb_hogaddr script type on the hogaddr outputs.
As flat Parquet files under a stable layout, one prefix per table, files named by block range. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. Files stay available for 7 days from delivery.
Join inputs.output_tx_hash to outputs.tx_hash and inputs.output_index to outputs.output_index. Each input names the output it spends, so a spend chain is a repeated self-join rather than a node replay.
One DuckDB line reads a whole table: SELECT * FROM read_parquet('outputs/*.parquet'). Values come in LTC, the smallest unit and USD at block time, so no decimal adjustment is needed.
A purchase covers full history from the genesis block to the day before the files are cut. Files are cut by block range, so any window can be assembled exactly.
Yes. Every table links to a public sample Parquet file with real records from one day, and the sample repository shows the first rows of each in the browser.
Every bonding-curve trade, token creation, migration and pool on Pump.fun, plus per-token OHLCV, decoded and USD-priced.
Every TRX, TRC-10 and TRC-20 transfer on TRON since June 2018, one row per transfer, valued in USD where a price exists.
Every native ETH and token transfer on Ethereum since August 2015, one row per transfer, valued in USD where a price exists.
Tell us the chain, tables and date range.