Browse

Kalshi hourly Ethereum price order book, live

Public
Explore tables

Kalshi hourly Ethereum price order book, live

Measure quoted liquidity in Kalshi hourly Ethereum strike markets. This dataset records event-driven YES order book states for open ETH above-threshold contracts from 2026-09-10 15:30 UTC onward. Use it to reconstruct quoted books at recorded seconds, measure spreads and depth, or compare liquidity across strikes near settlement.

Each row is one market ticker and second, holding the book after the last event in that second. Recording follows open strikes with a resting YES bid. Far strikes appear only when their book changes, and disconnected minutes are gaps.

Coverage

  • Window: from 2026-09-10 15:30 UTC onward, growing with every sealed segment, in UTC.
  • Grain: one row per market ticker and second, holding the book after the last event of that second.
  • Cadence: a new hourly event opens with a ladder of strikes. The recording follows every open strike that carries a resting YES bid. Strikes near the current Ethereum price produce several rows a minute. Far strikes produce a row only when their book changes.
  • Freshness: the recorder seals a segment every 300 seconds and each segment becomes a new table version.

Columns

  • ticker: the Kalshi market ticker, for example KXETHD-26SEP1012-T1749.99, naming the window and the strike.
  • timestamp_ms: the venue event time of the last book event in the second, in epoch milliseconds.
  • sequence: the final book event's position in the recording's arrival order.
  • best_bid, best_ask: the best resting YES bid and ask, in cents from 0 to 100.
  • bid_depth, ask_depth: the total resting contracts on the YES bid side and the YES ask side.
  • yes_bids, yes_asks: JSON arrays of {price, size} for every resting level, best price first, in cents and whole contracts.
  • ingest_time_ms: when the recorder received the frame, in epoch milliseconds.

Missing values

A side with no resting orders has a null best price, a depth of 0 and an empty ladder. A settled market stops producing rows. Any minute in which the recorder was not connected is a gap. Nothing before the recording started can be recovered.

Suitable for

  • Reconstructing the full YES limit order book of any hourly Ethereum strike at any second.
  • Measuring spread, depth and imbalance across strikes as the window approaches settlement.
  • Comparing hourly strikes with the 15-minute Ethereum contracts on Kalshi at a shared timestamp.
  • Studying how order flow reacts to moves in the CF Benchmarks reference price.

Source and rights

Kalshi's public trade API websocket, orderbook_snapshot and orderbook_delta channels, recorded under the workspace's own Kalshi API key. Settlement follows the CF Benchmarks Ethereum reference price at the end of each hourly window. Use is governed by Kalshi's API terms. No open licence is claimed by the publisher.

Tables

Table healthLivekalshi_eth1h_orderbookTable detailsNamekalshi_eth1h_orderbookColumns10
Table overviewPublished rows153,171Columns10 rows10 cols
Update detailsStatusLiveLast published9 Oct 2026

Sources

1 publisher
api.elections.kalshi.comapi.elections.kalshi.com1 endpoint
Website
api.elections.kalshi.com
Usage rights
Allowed by terms of service.
Requests
1 request across 1 endpoint
EndpointRequests / coverage
/trade-api/ws/v2Live order book snapshots and deltas for every open strike of the series that carries a resting YES bid (Kalshi KXETHD).1 request

Details

Contents
1 table · 153,171 rows · 10 columns
Coverage
—
Update cadence
Daily
Category
Crypto
Updated
Published
Version
2026-10-09
Visibility
Public
Publisher
Mostly Right

Access

Read published metadata and available row previews without an account or API key. A free account is required for full table downloads and API queries.

MCP endpoint
https://mostlyright.md/api/mcp · Public discovery and previews; sign in for queries.

Activity

Views167+167 in the last 30 days
Likes0+0 in the last 30 days
Uses1+1 in the last 30 days

Comments

0

No comments yet. Questions about coverage, licensing, or how a column is derived belong here, in the open, beside the data.

Sign in to join the conversation.