Historical Data - Hyperliquid Market Archives
Access Hyperliquid historical data including archival blockchain state, OHLCV candlesticks, tick-by-tick trade executions, order statuses, and order book diffs from Dwellir.
Dwellir preserves Hyperliquid node data in its source record formats and offers processed datasets for analysis. This page is the single inventory for S3 Bucket contents, formats, access, and product selection.
S3 bucket coverage
| Prefix | From | To | Object shape |
|---|---|---|---|
replica_cmds | 2025-01-12 | Current | LZ4-compressed native records |
node_trades | 2025-03-22 | 2025-06-21 | .lz4 |
node_fills | 2025-05-25 | 2025-07-27 | .lz4 |
node_fills_by_block | 2025-07-27 | Current | hourly .lz4 |
node_order_statuses_by_block | 2026-01-22 | Current | hourly .lz4 |
node_raw_book_diffs_by_block | 2026-01-22 | Current | hourly .lz4 |
misc_events_by_block | 2026-07-01 | Current | hourly .lz4 |
node_twap_statuses_by_block | 2026-07-01 | Current | hourly .lz4 |
orderbook_snapshots | 2026-04-29 | Current | <height>.json.lz4 |
periodic_abci_states | 2026-04-14 | Current | <height>.rmp.lz4 |
Archive formats
Native JSON and JSONL payloads are LZ4-compressed. Decompress .lz4 objects before parsing the record shape for their prefix. Generated order-book snapshots use <height>.json.lz4, while periodic ABCI state uses <height>.rmp.lz4. The latter contains RMP-encoded node state, not JSON.
Most current *_by_block feeds use an envelope with local_time, block_time, sequential block_number, and a feed-specific events array. The replica_cmds records contain abci_block and execution responses. Its abci_block.round is a consensus round, can skip, and must not be treated as the sequential block number.
The fills history spans 3 stored prefix generations:
| Prefix | Native shape | Useful fields |
|---|---|---|
node_trades | Trade record with a side_info array for participants | coin, side, time, px, sz, hash, participant order IDs |
node_fills | User address paired with a fill object | Price, size, direction, PnL, fee, order ID, trade ID, and fee token |
node_fills_by_block | Block envelope containing per-account fill events | Current fill fields plus block context and builder attribution |
Observed objects for these generations overlap, so their bounds are not mutually exclusive schema cutover dates. Select the parser from the object prefix and record shape. For processed analysis, tick data converts node_fills_by_block records into CSV or Parquet. For query access, use the Hyperliquid Index fills API.
Current field-level references are available for blocks, fills, order statuses, raw book diffs, misc events, and TWAP statuses.
Order-book reconstruction requires a known state seed, such as an orderbook_snapshots object generated from periodic ABCI state, followed by ordered node_raw_book_diffs_by_block records. Raw diffs alone cannot establish the starting book.
Choosing a historical product
| If you need | Use |
|---|---|
| Native blocks, fills, order events, book diffs, misc events, TWAP events, snapshots, or ABCI state | S3 bucket coverage above |
| Full-resolution trades in a columnar or spreadsheet-friendly format | Tick data |
| Wallet, builder, market, or historical-order queries over an API | Hyperliquid Index fills |
| 1s, 1m, or 5m price bars and exports | OHLCV data |
| Live L2/L4 books, BBO, and trades | Order Book WebSocket |
| Live raw feeds or derived V3 market streams | gRPC streaming |
To discover symbols before requesting data, use the Info endpoint. Perpetual names come from meta; spot names come from spotMeta.
Real-Time Data
For live market data, see:
- Order Book Server - Real-time L2/L4 order books and trades
- gRPC Streaming - StreamBlocks, StreamFills, and more
Access
For OHLCV data: sign up at the dashboard and visit the OHLCV Data tab to buy export credits and generate CSV or Parquet files for any market at 1s, 1m, or 5m intervals.
For S3 Bucket archival data, tick data, and other historical products:
Email: support@dwellir.com
Include in your request:
- Prefix or data product needed
- Date range
- Preferred format
- Use case description
web3_sha3
Compute the Keccak-256 hash of given data on Hyperliquid. Useful for hash verification, smart contract development, and data integrity checks.
Tick Data - Historical Trade Executions
Explore processed Hyperliquid trade-execution records with millisecond source timestamps. Tick-by-tick data is derived from node_fills_by_block for backtesting and market analysis.