Overview

Allium provides comprehensive realtime (datastreams) and historical data for Hyperliquid. The data is indexed from our in-house nodes that we operate. We run three nodes concurrently to ensure high availability and data completeness. We have included guides on how to navigate Hyperliquid data and FAQs on the data.

This section is for the Hyperliquid L1. Click here if you are looking for the EVM-compatible blockchain HyperEVM

Data Delivery & Interfaces

We offer the following delivery methods for both historical and near realtime data for Hyperliquid.

Explorer

Via the Allium App or Explorer APIs (Historical Data)

Datashares

Via Snowflake, Databricks, Google Cloud (Historical Data)

Datastreams

Via Kafka, Pub/Sub (Near Realtime Data)

Realtime APIs

Via API Endpoints

Historical Data CaveatsHyperliquid DEX Trades

Hyperliquid DEX Trades are fully backfilled for every address, except for ~4,000 traders (~1% of traders) who had made more than 10k trades at the time of backfill in March 2025.
This is because the Hyperliquid API only makes the last 10k trades available, and there are no other ways to retrieve the missing historical data. This means the following data is available:
Pre-March 2025: all trades are available for all addresses, except for ~4,000 traders, where only the last 10k trades are available
March 2025 onwards: all trades are available for all addresses

Hyperliquid Orders

Hyperliquid Orders cannot be backfilled. Data is available since we started running nodes in house. We minimise the possibility of missing out orders by running three nodes. Gaps may exist in the unexpected event of node failures.

Data Schemas

The following data schemas are available:

Using hyperliquid.dex.trades is recommended as it enriches the raw.trades table with relevant trade & token metadata, including HIP-3 permissionless perpetual details.

Table Name	Description
`hyperliquid.metrics.overview`	Daily overview metrics for Hyperliquid, including trading volume, fees, open interest, liquidations, bridge flows, and HIP-3 activity.
`hyperliquid.dex.trades`	Enriched DEX trades for spot and perpetual markets, including HIP-3 permissionless perpetuals, with granular fees, PnL, and positions.
`hyperliquid.assets.transfers`	Token transfers on Hyperliquid L1. Currently only includes deposits & withdrawals for Arbitrum.

Raw Data Schemas

Table Name	Description
`hyperliquid.raw.fills`	Raw Hyperliquid fills data.
`hyperliquid.raw.orders`	Raw Hyperliquid orders data.
`hyperliquid.raw.blocks`	Blocks level metadata, including block height, hash, timestamp, and proposer.
`hyperliquid.raw.transactions`	Transactions data for each block on Hyperliquid.
`hyperliquid.raw.tokens`	List of tokens that are traded on Hyperliquid DEX, with token metadata such as token name and symbol. Currently only includes spot tokens.
`hyperliquid.raw.perpetual_markets`	Perpetual markets metadata including HIP-3 permissionless perpetual DEXes, leverage settings, and market configuration.
`hyperliquid.raw.builder_fills`	Fills completed builders, including builder fees and the builder address from 2024-10-27
`hyperliquid.raw.builder_transactions`	Successfully completed transactions with builder address and fee, built incrementally from `hyperliquid.raw.transactions`
`hyperliquid.raw.builder_labels`	Builder address and builder identity mapping, source from publicly available data.
`hyperliquid.raw.register_referral`	Successfull referral registration filetered from `hyperliquid.raw.transactions`. Contains the referral code used `e.g. PURS` and the address of the user registering the referral.
`hyperliquid.raw.set_referrer`	Sucessful registration of a referrer filtered from `hyperliquid.raw.transactions`. Contains the referral code used `e.g. PURS` and the address of the user settingt the referrer.

Data Characteristics

In this section, we explain some of the characteristics of Hyperliquid data.

The hyperliquid.dex.trades table now includes granular columns for fees, PnL, positions, and liquidation details that were previously only available in the extra_fields JSON column of raw.trades. These include:

Fees: fee_token, seller_fee, buyer_fee, seller_builder_fee, buyer_builder_fee
PnL & Positions: seller_closed_pnl, buyer_closed_pnl, seller_start_position, buyer_start_position
Trade Direction: seller_dir, buyer_dir, seller_crossed, buyer_crossed
Order IDs: seller_order_id, buyer_order_id, seller_twap_id, buyer_twap_id
Liquidation: liquidated_user, liquidation_mark_price, liquidation_method
HIP-3: perp_dex, perp_market_name, perp_dex_deployer, perp_dex_fee_recipient, is_hip3

In most cases, the trade_id can be thought of as the unique identifier for a trade. However, there are cases where this isn’t true:

Before 24 Nov 2023: For historical Hyperliquid trades before 24 Nov 2023, the trade_id for all trades was 0. For those trades, we construct a unique_id from other values.
After 24 Nov 2023: There are a handful of trades where the Hyperliquid API returns the same trade_id for trades from different transactions. Because of this, we use the combination of trade_id and transaction_hash unique identifier for trades.

You can maybe find null transaction hashes, these are TWAPs

0x0000000000000000000000000000000000000000000000000000000000000000

See Hyperliquid TWAP for more details.A transaction with action “Place TWAP order” will look like the one linked in the; [Hyperliquid Explorer](https://app.hyperliquid.xyz/explorer/tx/0xd6f17b6efa51bd1a1ff30420be17af02015400689f842aff45bb18a090bd8c44Once such a transaction is sent multiple, orders will be placed within the specified time range, these will have a null transaction hash.

The hyperliquid node currently does not save order statuses unless the order already exists. Therefore open is not saved into the file, that the node generates, which is the source of this data.
For all the statuses the orders currently have run:

SELECT DISTINCT status
FROM hyperliquid.raw.orders
ORDER BY status;

is_trigger field is either true or false.
In the case where is_trigger is true the field

Every transaction has an action.

You can see all the different types of actions by running

SELECT DISTINCT action:type from hyperliquid.raw.transactions;

The above query can take a while to run

for quicker query for a subset (may be missing some types)

SELECT DISTINCT action:type from (select * from hyperliquid.raw.transactions limit 100000000);

Data Verticals

Solana

Hyperliquid

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

Overview

Data Delivery & Interfaces

Explorer

Datashares

Datastreams

Realtime APIs

Data Schemas

Raw Data Schemas

Data Characteristics

Overview

Data Verticals

Solana

Hyperliquid

Bitcoin Ecosystem

EVM

Cosmos Ecosystem

Move Ecosystem

Other Ecosystems

​Data Delivery & Interfaces

Explorer

Datashares

Datastreams

Realtime APIs

​Data Schemas

​Raw Data Schemas

​Data Characteristics

Data Delivery & Interfaces

Data Schemas

Raw Data Schemas

Data Characteristics