blocks
12 columnsOne row per block: size, difficulty, chainwork and transaction count.
zcash/blocks<start_block>_<end_block>.parquetone file per block rangeThe full Zcash ledger since October 2016: blocks, transactions with shielded counts, and transparent inputs and outputs with ZEC and USD values.
Every Zcash block and transaction from the genesis block in October 2016 to yesterday, with the transparent inputs and outputs of each transaction decoded to address, script type and value in ZEC, zatoshi and USD at block time.
Shielded transfers (Sprout, Sapling and Orchard) hide their amounts and addresses on chain, so they have no input or output rows. Each transaction row counts its shielded spends, shielded outputs and JoinSplits and carries the net value that moved between the transparent and shielded pools, so pool flows are a sum over transactions. Files are cut by block range and named by their first and last block.
One row per block: size, difficulty, chainwork and transaction count.
zcash/blocks<start_block>_<end_block>.parquetone file per block rangeOne row per transaction with input, output, fee and mined values in ZEC, zatoshi and USD.
zcash/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.
zcash/inputs<start_block>_<end_block>.parquetone file per block rangeOne row per transaction output with address, script type, change heuristic and value.
zcash/outputs<start_block>_<end_block>.parquetone file per block rangeblocks12 columnsOne row per block: size, difficulty, chainwork and transaction count.transactions29 columnsOne row per transaction with input, output, fee and mined values in ZEC, zatoshi 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, delivered as signed download links by email after payment, in this layout:
# blocks: one file per block range zcash/blocks<start_block>_<end_block>.parquet # transactions: one file per block range zcash/transactions<start_block>_<end_block>.parquet # inputs: one file per block range zcash/inputs<start_block>_<end_block>.parquet # outputs: one file per block range zcash/outputs<start_block>_<end_block>.parquet
Four Parquet tables: blocks, transactions, inputs and outputs, covering full history from the genesis block to yesterday. Inputs and outputs are the transparent ones; every row carries its address, script type and value in ZEC, zatoshi and USD.
Every transaction is listed in the transactions table, including fully shielded ones, with its shielded spend, shielded output and JoinSplit counts and its shielded balance. Their shielded amounts and addresses are not on chain, so they have no rows in inputs or outputs.
As flat Parquet files under a stable S3 layout, one prefix per table, files named by block range. Signed HTTPS links are emailed once the files are prepared.
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 ZEC, 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.