Crypto Price History

One Parquet table, currency_ohlcv_1d, with 15 columns: the day, the currency, USD open, high, low and close, USD and coin volume, the number of hourly bars behind the day, and four supply figures including market cap. About 8,900 rows for 300 currencies over 30 days.

About 8,900 rows and roughly 1 MB as Parquet, estimated from a one-day sample at 141 bytes per row. The export for the 30 days to 8 October 2026 returned 8,862 rows; exact figures arrive with the delivery manifest.

Currencies are ranked by their median market cap over the 30 days, counting only bars where the circulating supply is known, with a floor of $100,000 traded in the window. The list is fixed when your order is built and shipped inside the file.

30 days. The price index keeps 30 days of bars, so that is the longest window this dataset can hold. Each order is built once, when you buy, and covers the 30 days up to the latest full UTC day. It is a fixed set of files and does not update afterwards. For prices that keep updating, use the Bitquery Trading API.

Prices come from the Bitquery price index, the same series the Trading API serves. A daily bar is rolled up from the 24 hourly bars: open of the first hour, close of the last, highest high, lowest low, summed volume. We ran the export for two windows before release. Both returned every day in the window, and no bar had a high below its low.

Coins with no trading on the ten chains we cover, coins with no known circulating supply, and coins that traded under $100,000 in the window. Centralized exchange trades are not in the source. Days with no trade have no row.

Supply for a coin such as Bitcoin counts its wrapped copies on the chains we cover, not the native supply, so its market cap here is far below the figure on a price site. A few coins appear under more than one Currency_Id when a bridged copy has not been grouped with the main one. Prices are 32-bit floats in the source, good to about seven digits.

No. Every price here is built from on-chain DEX trades. For widely traded coins it follows exchange prices closely; for a coin with thin DEX trading it can differ or have gaps.

One line in DuckDB: SELECT * FROM read_parquet('currency_ohlcv_1d/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path).

Each order is built once, when you buy, and covers the 30 days up to the latest full UTC day. It is a fixed set of files and does not update afterwards. For prices that keep updating, use the Bitquery Trading API. 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.