tickfoundry
capture livesign inget the data →
hyperliquid historical data / kLUNC
§perpetuals

kLUNC on Hyperliquid, tick by tick.
Order book and trades, 2025-01-252026-09-10.

The complete order-book and trade history of the kLUNC perpetual on Hyperliquid: top of book on every change, the 25-level book on every change with resting-order counts, and every fill with the taker's wallet, fee and realized PnL — rebuilt from the chain's own order-event stream, one row per block.

594 days2025-01-252026-09-10 · gapless · ~32 MB per day · 18 GB on disk
pull kLUNC days →schemapricing

What a kLUNC day contains

Three parquet files per day plus a quality scorecard. Sizes are this coin's own averages over its 594 days on disk.

Top of book (every change)hl_l1

Best bid and ask with sizes and the spread, one row per block in which the top of book changed, replayed from the chain's own order events — not sampled from a websocket. No consecutive duplicates.

~2 MB per kLUNC day
Order book — 25 levels, every changehl_l2

The 25-level book on both sides — price, size and the number of resting orders at each level — one row per block in which any of it changed. Wide columns (bid_px_1 … ask_n_25), unused levels null. This is the table the venue's own websocket cannot give you: Hyperliquid pushes l2Book snapshots only, throttled to seconds.

~30 MB per kLUNC day
Trades (fills)hl_trades

Every fill the chain executed: price, size, taker side, order id, the taker's wallet, fee and fee token, closed PnL and start position, and the settlement transaction hash. From 2025-03-22 straight from the node's fills tape; before that synthesized from the taker's own fill status (see caveats).

~162 kB per kLUNC day

Coverage notes for kLUNC

  • First day on disk: 2025-01-25. That is the first day of the archive itself, not the coin's listing date.
  • One row per block. Blocks land about every 70 ms; a book row exists for every block in which the book changed, so quiet hours are short and busy hours are long. msg_seq is the block height.
  • Fills before 2025-03-22 are synthesized. No fills tape exists upstream before 2025-03-22, so taker fills in that era are derived from each taker order's own filled size and average price against the resting book (source_event_type = l3_taker_status). price, size, side, oid and user are set; transaction_hash, tid, dir, fee, fee_token, closed_pnl and start_position are null. Resting orders that expired or were cancelled without an event can linger in the book until the order-id-gap inference catches them.
  • Spot books start unseeded. The archive has no snapshot before its first day, so resting spot depth is thinner than steady state for the first day or two.
  • A 924-block hole on 2025-07-19. Heights 668379075 onward, roughly the last minutes of one source object: the object is truncated in Hyperliquid's own bucket. Every coin is affected for that interval; nothing else that day.
  • Every bundle ships kLUNC's quality scorecard per day — agreement with the venue's own published book snapshots — and a README that states these notes for your exact range.

Pricing

Building this yourself — pulling the chain's order-event archive out of requester-pays S3 and replaying it into books — runs to around $10,000 in egress and compute. Every coin arrives in the same objects, so there is no kLUNC-only shortcut.

A quarter of kLUNC — every table — is about 2.9 GB. Explorer ($89/mo) and Premium ($199/mo) bought for Hyperliquid include every coin at full book depth; $50/mo adds Hyperliquid to a Polymarket plan. Any free account pulls 2026-08-12 at no cost.

start Premium for Hyperliquid →browse the catalog

Other perpetuals on Hyperliquid

BTCETHHYPESOLFARTCOINSUIWLDDOGEENAVIRTUALAVAXTAOWIFAAVESPXXRPTIAPENGULINKADAZECPOPCATTRUMPLDO… the whole venue
kLUNC Hyperliquid historical data — order book and trades, tick by tick, 2025-01-25 → 2026-09-10 · TickFoundry