Zebra Node Operations & Sync

Real-time health, sync progress, P2P topology, mempool footprint, and RPC performance.

Active Connection:3rd-Party Remote RPC

Connected to Live Node

Zebra Node Sync HUD

Fully Synchronized—

Current Tip: —At Network Head (#0)

Zebra Node Diagnostics

Live telemetry from your connected Zebra (zebrad) full node over JSON-RPC.

Block Height (Tip)

The highest validated block on the chain.

P2P Peers

Connected network nodes sharing blocks and transactions.

Mempool

Pending unconfirmed transactions waiting to be mined.

Sol/s (Hashrate)

Proof-of-Work computational mining power securing the network.

Endpoint health

Height

chain tip as this node sees it

Sync Progress

at the tip

Peers

getpeerinfo unavailable

Mempool

size only

Network Hashrate

getnetworksolps

Node Version

getinfo / getnetworkinfo

RPC surface probed

probing the node…

What the node implements is probed by calling each method once and reading the error: JSON-RPC returns −32601 for a method that does not exist, and any other error proves the method is there. Which software it is comes from its own user agent.

RPC query telemetry

Total Calls

queries executed

Successful

valid responses

Errors

failed queries

Live telemetry tracking all JSON-RPC calls sent to the connected Zebra node.

Per-method latency

Method	Calls	Errors	Last	Avg	Min / max	Recent	Last called
No calls recorded yet in this process.

Measured inside the transport on every call, so these are the timings the app actually experienced — not a synthetic ping.

Poller history

no samples yet

Nothing recorded yet. Run "npm run poll" next to the dev server, or point a scheduler at /api/cron/poll, and these fill in.