Every Cardano block, transaction, input and output from the Byron genesis in September 2017 to yesterday, with ADA values in lovelace, ADA and USD at block time. Each input and output has one row for its ADA amount and one more row for every native asset it carries, so tokens and NFTs are traced with the same joins as ADA. Payment addresses come with their stake key, and transactions carry their metadata.
Inputs carry the hash and index of the output they spend, and a mints table records every native asset minted or burned, so supply and flow of any asset are two joins. Files are cut by block range and named by their first and last block, so any window can be assembled exactly.
Use cases
Extended UTXO graph analysis and address clustering by stake key
Native asset and NFT flow tracing across mints, inputs and outputs
Fee, deposit and withdrawal research from Byron to the current era
Coin-age and dormancy studies from spend links
5 tables
97 columns · free sample for each table
blocks
17 columns
One row per block: size, transaction count, fees, epoch, slot and slot leader.
cardano/blocks<start_block>_<end_block>.parquetone file per block range
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.
Delivery
Parquet files, delivered as signed download links by email after payment, in this layout:
# blocks: one file per block range
cardano/blocks<start_block>_<end_block>.parquet# transactions: one file per block range
cardano/transactions<start_block>_<end_block>.parquet# inputs: one file per block range
cardano/inputs<start_block>_<end_block>.parquet# outputs: one file per block range
cardano/outputs<start_block>_<end_block>.parquet# mints: one file per block range
cardano/mints<start_block>_<end_block>.parquet
Download a free sampleNo email needed.
Pay nowName, work email and licence check.
Pay the invoiceBy card or bank transfer.
Get signed linksThe team prepares the export and emails the links.
Five Parquet tables: blocks, transactions, inputs, outputs and mints, covering full history from the Byron genesis to yesterday. Every input and output carries its payment address, stake key, currency and value; native assets are separate rows keyed by token_index.
Are native tokens and NFTs included?
Yes. An output that carries ADA and two native assets is three rows: token_index -1 for ADA and 0 and 1 for the assets, each with its currency id, symbol, name, decimals and raw amount. The mints table lists every asset minted or burned, with negative amounts for burns.
How is the data delivered?
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.
How do I trace where coins went?
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.
How do I load it?
One DuckDB line reads a whole table: SELECT * FROM read_parquet('outputs/*.parquet'). Values come in ADA, the smallest unit and USD at block time, so no decimal adjustment is needed.
How current is the data?
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.
Can I try before I buy?
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.