> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Timestamps

> Which clock each 0xArchive time field reads, its unit and precision, the block fields beside it, and when it is null.

Every time 0xArchive sends is in UTC and reads one of two clocks. Event time is the venue's own time: Hyperliquid's block time or trade time, or Lighter's trade time. Trades, L4 order events, Hyperliquid order books and trigger levels carry it. Observation time is when 0xArchive read the data. Hyperliquid's market context (funding, open interest, mark and oracle prices) has no time of its own, so those rows carry the time we read them.

When the API does not know the time of an order book, a summary or a trigger-level map, the field is `null`. It is never `0` and never the time of your request.

## Clock by data type

| Data | Field | Clock | Precision |
| - | - | - | - |
| Trades and fills | REST `timestamp`, WebSocket `time` | Venue execution time | Milliseconds |
| Liquidation events | `timestamp` | Venue execution time | Milliseconds |
| L4 order events | REST `timestamp` with `block_number`, WebSocket `ts` with `bn` | Hyperliquid block time | Milliseconds |
| L4 order book | `timestamp`, `last_block_number` | Block time of the last block applied to the book | Milliseconds |
| Full-depth L2 order book | `timestamp` | Block time of the last block applied to the book | Milliseconds |
| Full-depth L2 diffs | `timestamp`, `block_number` | Block time of the block that produced the diff | Milliseconds |
| Native L2 order book, Hyperliquid core and HIP-3 | `timestamp`, `source` | `venue`: Hyperliquid's time on the book message. `node`: a fixed grid in chain time | Milliseconds |
| Candles | `timestamp` | Start of the bar | Bar start |
| Funding and open interest, Hyperliquid | `timestamp` | Observation time | Milliseconds |
| Funding and open interest, Lighter | `timestamp` | Lighter's time on the market-stats update, or observation time when the update has none | Milliseconds |
| Market summary | `timestamp` | Time of the funding and open-interest sample the summary is built from | Milliseconds |
| Trigger levels | `as_of`, `as_of_block` | Block time of the newest trigger-order event in the map | Milliseconds |
| Trigger-level history | `snapshot_ts` | When 0xArchive took the snapshot | Seconds |
| Projected forced-liquidation price levels | `snapshot_ts`, `block_number` | When 0xArchive computed the snapshot, since August 13, 2026 | Seconds |
| Lighter order book | `timestamp` | Time of the book's last recorded change | Milliseconds |
| Lighter L3 order book | `timestamp` | When 0xArchive read the book from Lighter | Milliseconds |

Several fills can share one millisecond, so a timestamp alone does not order them. L4 events order by block, as [L4 order book](https://docs.0xarchive.io/websocket/l4-orderbook.md) describes.

## Units and formats

| Where | Format |
| - | - |
| REST responses | RFC 3339 strings in UTC. Most end in `Z`; the full-depth `/l2` routes end in `+00:00`, so parse both forms. A few fields send integer milliseconds unless you send `0xArchive-Version: 2026-10-01`, as [API conventions](https://docs.0xarchive.io/conventions.md#versioning) lists |
| WebSocket messages | Unix milliseconds as integers: `time` on trades, `ts` on L4 events, and `timestamp` on `l4_snapshot` and replay messages |
| Requests | Unix milliseconds or RFC 3339 for `start`, `end`, `timestamp` and `at`; see [Parameters](https://docs.0xarchive.io/rest-api/parameters.md). An order-book `timestamp` outside the supported range returns `400` with `invalid_time_range` |
| Lighter `transaction_time_us` | Microseconds. It appears on Lighter liquidations and on canonical Lighter trade rows |

## Order books

### L4

The latest L4 book from REST carries the block time of the last block applied to it, with `last_block_number`. A book requested with `timestamp=T` carries `T`, the instant you asked for. Each L4 diff carries its block's time and `block_number`.

On WebSocket, an L4 subscription opens with an `l4_snapshot` whose `timestamp` is the block time of the last block applied to the book, in Unix milliseconds, or `null` while that block time is not known. Every `l4_batch` item carries `ts` and `bn`. A replay opens with the `l4_snapshot` of its starting checkpoint, carrying that checkpoint's time.

L4 checkpoints carry their block's time from October 23, 2026. Older checkpoints carry the time they were read, which can be later than their block, so align them by `last_block_number`.

### Full-depth L2

`/l2` books, `/l2/history` books and the `orderbook_full` and `hip3_orderbook_full` snapshots carry the block time of the last block applied to the book. The latest `/l2` book and the WebSocket snapshot are `null` while that block time is not known. Each `/l2/diffs` row carries its own block's time and `block_number`. WebSocket level changes carry `bn` and no time; place them by block after the snapshot.

Data stored before November 14, 2026 keeps the times it was written with. A checkpoint from before that date can carry its write time, and diffs from before it can share one time for every diff written in the same minute. Order those diffs by `block_number`.

### Native L2

Native Hyperliquid core and HIP-3 L2 history holds two sources, named in `source`. A `venue` row carries Hyperliquid's time on the book message. A `node` row sits on a fixed grid in chain time: it is the book after every block with a block time at or before its `timestamp`. The two sources keep different clocks, so a `venue` row and a `node` row with the same timestamp can show different books. [L2 order books](https://docs.0xarchive.io/rest-api/order-books-l2.md#two-sources-in-native-core-and-hip-3-history) has the cadences.

### Lighter

A Lighter book's `timestamp` is the time of its last recorded change, or of its checkpoint when nothing changed after it, at or before the instant you requested. For the latest book, that is the last recorded change, not the time of your request. At `30s`, `10s` and `1s` granularity, `/orderbook/{symbol}/history` stops at the book's newest recorded change instead of repeating the last book up to `end`. Lighter L3 snapshots carry the time 0xArchive read the book.

## Candles

A candle's `timestamp` is the start of its bar in UTC. The bar holds the trades at or after that time and before the next bar starts.

In WebSocket replay, a candle arrives at its bar's start time and already carries the completed bar's open, high, low, close and volume. For a point-in-time backtest, act on a bar only from its end: `timestamp` plus the interval.

## Funding and open interest

Hyperliquid's market context carries no time, so on Hyperliquid core, HIP-3 and HIP-4 a funding or open-interest `timestamp` is when 0xArchive read the sample. Older Hyperliquid core rows come from Hyperliquid's own archive and fall on the whole minute; [Venue coverage](https://docs.0xarchive.io/venue-coverage.md) has the dates. Lighter rows carry the time on Lighter's market-stats update, or the time 0xArchive received the update when it has none.

Hyperliquid funding rows are samples of the current rate, not settlements. For funding a wallet paid or received, use [Funding payments](https://docs.0xarchive.io/rest-api/positions.md#funding-payments).

Live `open_interest` and `funding` WebSocket frames carry no time. Replayed frames carry the stored sample's time in `timestamp`.

## Market summary

A `/summary/{symbol}` `timestamp` is the time of the market-context sample its prices, open interest and funding come from. When the open-interest and funding samples differ, it is the older of the two. HIP-4 has no funding and uses the open-interest sample. The trailing 24-hour volume and liquidation totals do not move it. It is `null` when no sample was available.

## Trigger levels and projected forced-liquidation price levels

On the [trigger-level](https://docs.0xarchive.io/rest-api/tpsl.md) snapshot route, `as_of` is the block time of the newest trigger-order event the map reflects, to the millisecond, and `as_of_block` is the last Hyperliquid block the map reflects. `as_of_block` can be later than the block of the `as_of` event when no trigger order on the venue changed in the blocks after it. Both are `null` when unknown, and a cached answer keeps the time of the data it was built from. Trigger-level history rows carry `snapshot_ts`, the time 0xArchive took each snapshot.

The [projected forced-liquidation price-level endpoints](https://docs.0xarchive.io/rest-api/liquidation-levels.md) carry `snapshot_ts` and `block_number`, which describe different moments. Since August 13, 2026, `snapshot_ts` is when 0xArchive computed the snapshot, and `block_number` is the block of the exchange-state snapshot it started from, typically 30 to 65 minutes earlier. [Timing and provenance](https://docs.0xarchive.io/rest-api/liquidation-levels.md#timing-and-provenance) covers older rows.

## Next step

**Order events by block**

Rebuild an L4 book from a snapshot and its ordered batches, keeping block numbers and gap state with the result.

[Apply L4 events](https://docs.0xarchive.io/websocket/l4-orderbook.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.