hypercore dataset holds the standardized HyperCore tables. HyperCore is an exchange rather than a general-purpose chain, so where an EVM chain publishes logs and internal calls, HyperCore publishes the streams its matching engine emits: what filled, what was ordered, how the book moved, and what funding was settled.
Tables
| Table | Since | Description |
|---|---|---|
blocks | 2025-07 | One row per block, with the number of records each stream emitted in it. |
node_trades | 2025-03 | One row per side of a trade, the taker’s and the maker’s, in a slim shape: the account, market, side, price, size and whether that side was the taker. |
node_fills | 2025-07 | One row per fill, in the full shape: the fee and the token it was paid in, the builder credited, the position direction and the liquidation fields where the fill closed a position. |
node_fills_without_block_number | 2025-05 to 2025-07 | The fills the node recorded before block numbers were attached to them, in the same shape as node_fills. |
node_funding | 2025-09 | One row per market per funding settlement, with the rate it applied and the amount settled on each side. |
events | 2025-09 | One row per exchange event outside trading, typed by event_kind and, for ledger updates, by ledger_type. |
orders | 2025-11 | One row per order status change, with the limit price, the size, the order type and the time in force. |
book | 2025-11 | One row per change to a resting order level, with the price and the level size before and after. |
twap | 2025-11 | One row per state change of a TWAP order, with the size and notional executed so far, and the stop price and trigger where the order sets them. |
writer_actions | 2025-12 | One row per action written into HyperCore from HyperEVM, such as a spot send or a delegation, with the EVM transaction that sent it. |
block_number, fills on block_number, coin and trade_id together with the account and side, trades on trade_timestamp, coin, trade_id and is_taker from 2025-05-25, orders and TWAPs on order_id and twap_id, and funding on the market and settlement time. coin is the market symbol as the venue lists it, and it is the join back to the market registries on Perpetuals.
Three columns hold JSON, because their shape depends on a type column: event_json in events, children in orders and action in writer_actions. Read the type column first, then extract the fields that type defines.
Sample queries
- Daily trading
- Busiest markets
- Funding settlements
Count daily trades and the accounts behind them.
node_trades holds one row per side of a trade, and the taker row counts each trade once. It is the slim trade stream, the lowest-cost table for volume and participation questions.