Binance ZECUSDT spot historical order book & tick data
941K trade and depth events for ZECUSDT on Binance spot since 2025-06-01 — about 1,838 events a day.
Coverage
ZECUSDT spot data coverage
What is recorded, how often it updates and how much there is.
History start
2025-06-01
512 days of history
Events recorded
940,800
≈ 941K as of 2026-10-25
Avg events / day
1,838
trade · depth update
Update frequency
Every trade tick-by-tick; depth diffs at 100 ms
Daily activity · last 30 days
Indicative daily event volume, last 30 days to 2026-10-25. Shape modeled from collector stats; mean matches the average events/day above.
About this market
What is ZECUSDT spot?
ZECUSDT has grown from a niche privacy pair into one of Binance spot's busiest alt markets, with bursty trading that follows headline cycles. AymarData has recorded 941K events on Binance spot ZECUSDT since 2025-06-01: every trade, plus order-book updates at 100 ms.
Zcash is a privacy coin with optional shielded transactions and a Bitcoin-style fixed supply schedule. The things that move ZEC on spot are, in rough order: the privacy narrative, which flares whenever regulators or analytics firms make headlines; shielded-pool growth, a slow-moving fundamental that traders watch as a sentiment gauge; and listing and delisting decisions by exchanges that are cautious about privacy assets. Each shows up in the data differently — as a burst of aggressive trades, as depth leaving one side of the book, or as a widening spread.
At roughly 1,838 events a day, ZECUSDT is liquid enough for 100 ms-level analysis but quiet enough that individual large orders are visible in the data. That makes it good for studying spread dynamics, queue behaviour around news and the way alt liquidity thins out during sector-wide drawdowns.
What moves ZECUSDT spot
- The privacy narrative, which flares whenever regulators or analytics firms make headlines
- Shielded-pool growth, a slow-moving fundamental that traders watch as a sentiment gauge
- Listing and delisting decisions by exchanges that are cautious about privacy assets
Schema
ZECUSDT spot fields and sample rows
The same columns are returned by the API and in Parquet and CSV files.
| Field | Type | Description |
|---|---|---|
| ts_ms | int64 | Exchange event time, Unix milliseconds |
| symbol | string | Binance symbol, here ZECUSDT |
| event_type | string | trade | depth_update |
| side | string | buy / sell for trades (taker side); bid / ask for depth |
| price | number | Trade price or book level in USDT |
| size | number | Base-asset quantity; 0 on a depth update means the level was removed |
Sample rows
| ts_ms | symbol | event_type | side | price | size |
|---|---|---|---|---|---|
| 1792679406739 | ZECUSDT | trade | buy | 410.72 | 7.013 |
| 1792679407078 | ZECUSDT | trade | sell | 410.71 | 9.074 |
| 1792679407378 | ZECUSDT | depth_update | bid | 410.69 | 5.766 |
Illustrative rows for ZECUSDT on Binance spot; prices are in USDT and shown for schema purposes, not as live quotes.
Code
Pull ZECUSDT spot in Python, cURL or MCP
Market id: ZECUSDT. Export AYMARDATA_API_KEY from your dashboard, then run the Python requests example.
import os
import requests
API = "https://api.aymardata.com/v1"
KEY = os.environ["AYMARDATA_API_KEY"] # export AYMARDATA_API_KEY=ad_live_…
H = {"Authorization": f"Bearer {KEY}", "User-Agent": "aymardata-docs/1.0"}
# ZECUSDT spot: five minutes of trades
trades = requests.get(
f"{API}/trades",
headers=H,
params={
"source": "binance-spot",
"market": "ZECUSDT",
"start": "2026-10-22T14:30:00Z",
"end": "2026-10-22T14:35:00Z",
"limit": 500,
},
timeout=30,
).json()["data"]
buys = [t for t in trades if t["side"] == "buy"]
print(f"{len(buys)} of {len(trades)} ZECUSDT prints were taker buys")
book = requests.get(
f"{API}/book",
headers=H,
params={
"source": "binance-spot",
"market": "ZECUSDT",
"at": "2026-10-22T14:32:00Z",
"depth": 10,
},
timeout=30,
).json()
print(book.get("spread"), len(trades))FAQ
ZECUSDT spot: common questions
Is ZECUSDT liquid enough for microstructure research?
Yes for 100 ms-level work: about 1,838 events a day is enough to measure spreads, depth and short-term impact, while quiet enough that single large orders stand out. For tight latency studies on a smaller pair, check the event gaps first.
What moves ZECUSDT on Binance spot?
Mainly the privacy narrative, which flares whenever regulators or analytics firms make headlines, and shielded-pool growth, a slow-moving fundamental that traders watch as a sentiment gauge. ZECUSDT has grown from a niche privacy pair into one of Binance spot's busiest alt markets, with bursty trading that follows headline cycles.
How much ZECUSDT spot data is there?
941K events since 2025-06-01, averaging 1,838 per day. Events carry the Binance exchange timestamp in milliseconds; trades record the taker side.
How does ZECUSDT spot compare with the ZECUSDT perpetual?
Spot is the cash reference; the perp adds mark price and funding. Joining the two on timestamp gives you basis and lead-lag — see the ZEC perp page for the matching feed.
How do I pull ZECUSDT spot trades with the API?
Call GET /v1/trades with source=binance-spot and market=ZECUSDT plus start and end timestamps (Python requests examples on this page). Ready to run with your API key.
Related
Related markets and next steps
Backtest ZECUSDT spot with real tick data
Get an API key, pull your first window and join it with the other sources in the catalog.