# Token Price History Daily | Bitquery Data Store Daily USD price history for the 1,000 most traded DEX tokens on ten chains, up to 12 months, one row per token and day. Dataset page: https://bitquery.io/datastore/datasets/token-price-history-daily Network: Multi-chain Category: OHLCV Tables: 1 Columns: 16 Coverage: first block to 2026-10-08 Rows: about 354K Format: Apache Parquet, ZSTD compression, one prefix per table Licence: https://bitquery.io/datastore/legal/data-license ## What this is We build one USD candle per token and day from decoded DEX trades, for the 1,000 tokens with the highest trading volume over the window you buy, on Solana, BNB Smart Chain, Base, Ethereum, Polygon, Arbitrum, Optimism, Tron, Robinhood Chain and Arc. The file holds price and volume only: no market cap or supply columns. A row is one token on one UTC day. Most buyers pivot Price_Ohlc_Close by Token_Id and Block_Date to get a price history table. Join on Token_Id, because symbols repeat, and read Interval_Bars to see how many hours of the day had a trade. ## What people use it for - A year of daily closes for a fixed list of 1,000 tokens - Return, drawdown and volatility tables over 6 or 12 months - DCA and recovery calculators that need daily prices - Backfilling daily price history into your own database ## Tables (1) ### token_ohlcv_1d: 16 columns One row per token and UTC day: USD open, high, low and close, and volume. Bucket prefix: multichain/price_history/token_ohlcv_1d File naming: .parquet, one file per UTC day Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/multichain/price_history/token_ohlcv_1d/2026-10-08.parquet | column | type | description | | --- | --- | --- | | Block_Date | Date | UTC day of the bar | | Token_Network | String | Chain the token trades on | | Token_Address | String | Token contract or mint address; empty for a chain's native coin | | Token_Id | String | Bitquery token id, the chain prefix plus the address; the join key | | Token_Symbol | String | Symbol reported by the token; not unique | | Token_Name | String | Name reported by the token; not unique | | Token_IsNative | Bool | True for a chain's native coin | | Currency_Id | String | Bitquery currency id that groups this token with its copies on other chains | | Currency_Symbol | String | Symbol of that currency | | Price_Ohlc_Open | Float64 | First USD price in the day | | Price_Ohlc_High | Float64 | Highest USD price in the day | | Price_Ohlc_Low | Float64 | Lowest USD price in the day | | Price_Ohlc_Close | Float64 | Last USD price in the day | | Volume_Usd | Float64 | USD value traded in the day | | Volume_Base | Float64 | Amount of the token traded in the day, decimal adjusted | | Interval_Bars | UInt32 | Hours of the day that had at least one trade, 1 to 24 | ## Price - Last 6 months (Apr 8, 2026 → Oct 8, 2026): $750 one-time, USD - Last 12 months (Oct 8, 2025 → Oct 8, 2026): $1,500 one-time, USD Every window includes all 16 columns. Only the time range changes. ## Questions buyers ask Q: What is in Token Price History Daily? A: One Parquet table, token_ohlcv_1d, with 16 columns: the day, the token and its chain, USD open, high, low and close, USD and token volume, and the number of hourly bars behind the day. Q: How big is it? A: About 350,000 rows for 12 months and half that for 6. This is an estimate scaled from the latest 30 days, which hold about 29,500 rows; exact figures arrive with the delivery manifest. Q: Which tokens and chains are included? A: The 1,000 tokens with the highest USD trading volume over the window you buy, on Solana, BNB Smart Chain, Base, Ethereum, Polygon, Arbitrum, Optimism, Tron, Robinhood Chain and Arc. The list is fixed when your order is built and shipped inside the files. Q: How far back does it go? A: You choose 6 or 12 months at checkout. Each order is built once, when you buy, and covers the 6 or 12 months up to the latest full UTC day. It is a fixed set of files and does not update afterwards. A chain younger than the window is covered from its first block, so a chain that launched three months ago has three months of rows. Q: How are the candles produced, and how was the sample checked? A: Candles are built from decoded DEX trades on each chain, priced in USD at trade time. No market cap or supply figures are included, which is what lets this dataset reach back a year. We read the published sample back before release: no duplicate bars, no blank names, and no bar with a high below its low. Q: What was left out, and why? A: Market cap and supply columns, trades on centralized exchanges, and days with no trade, which have no row. Nothing is forward filled. Q: What should I watch out for? A: Symbols and names repeat, so join on Token_Id. The same coin appears once per chain under a different Token_Id; Currency_Id groups those copies. These are DEX prices: for widely traded coins they follow exchange prices closely, and for a thinly traded token a bar can be missing. Q: How do I load it? A: One line in DuckDB: SELECT * FROM read_parquet('token_ohlcv_1d/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). The sample file opens without credentials. Q: How current is it, and how is it delivered? A: Each order is built once, when you buy, and covers the 6 or 12 months up to the latest full UTC day. It is a fixed set of files and does not update afterwards. Delivered as Parquet with ZSTD compression, one file per day, under a stable layout with a JSON manifest listing every file and its sha256. 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. ## 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.