Solana · blockchain observability

Is the RPC answering, and how fast?

ChainOptic treats a public Solana node like production infrastructure. It probes health, version, slot and throughput, times every round-trip it makes, reads the priority-fee pressure in recent blocks, and tails live traffic for a program you choose.

RPC Health

—

getHealth

Round-trip

—

measured in-browser

Core

—

getVersion

Slot

—

getSlot · epoch —

Throughput

—

TPS · non-vote

Slot time

—

ms/slot, recent

Throughput & slot time

recent performance samples

TPS (total)slot time

RPC latency

this session

now

—

avg

—

p95

—

Priority-fee pressure

µlamports / CU

Median

—

p90

—

Max

—

Paying slots

—

Reading recent slots…

Live activity tail

getSignaturesForAddress · limit 25

Program

Signature	Slot	Status	Idx	Seen
Waiting for first probe…

What "round-trip" means

Every probe is timed in the browser with a high-resolution clock, from request to parsed response. It mixes your network path and the node's own latency — the number an operator actually feels.

Reading fee pressure

getRecentPrioritizationFees returns the fee paid per compute unit across recent slots. When most slots sit at zero, blockspace is cheap; a rising median and a growing share of paying slots mean contention.

The activity tail

Signatures stream newest-first for the chosen program. A red marker is a transaction that landed but reverted — common and healthy — not an RPC fault.