Real time Solana volume data
The four routes a live volume number can travel, what each one guarantees, and why two dashboards watching the same token disagree at the same moment.
Read the noteWhere live Solana data actually comes from
Every real time number about Solana starts as a transaction inside a block, and ends as a value you read. Between those two points sits a transport, and the transport decides everything: how quickly you hear about the event, whether you hear about it twice, and whether you hear about it at all when your process was restarting.
This section covers the four transports in use today, in the order most people meet them. The bias throughout is towards what each one guarantees rather than how fast it feels, because a feed that is usually fast and occasionally silent is harder to work with than a feed that is predictable.
transports HTTP, WebSocket, gRPC, callback
replay Only HTTP history replays on demand
default commitment finalized on most RPC methods
shared failure A silent feed looks like a quiet market
4 notes in this section
Where a live number comes from before it reaches your screen: HTTP polling, WebSocket subscriptions, validator-level Geyser streams and provider webhooks, with the delivery guarantee each one gives you.
WebSockets versus polling
Pull and push are not two speeds of the same thing. Request budgets, missed events, reconnect behaviour and the hybrid most working systems end up running.
Read the noteLog subscriptions explained
What logsSubscribe actually delivers, the single-address limit on the mentions filter, log truncation, and why a log line is a hint rather than a ledger entry.
Read the noteWebhooks and push data
HTTP callbacks as a transport: at-least-once delivery, idempotency keys, ordering you do not get, and the receiver design that survives a provider retry storm.
Read the noteChoosing between them
There is no ranking here because the right transport depends on what you are building. A price ticker and a compliance ledger have opposite requirements, and a system that tries to serve both with one connection usually serves neither well. The practical answer for most live views is a subscription for immediacy plus an HTTP path for truth, with the second one deciding what is finally counted.
Latency The difference between a slot, a confirmation, a finalised root and a chart that has caught up. Where delay is added, which part of it is protocol and which part is pipeline. Open the section Building a view Turning a transaction stream into a number you would defend: decoding swaps from balance deltas, aggregating windows, alerting on movement and closing the gaps a stream leaves behind. Open the section