What is this?

The Network Status page provides a real-time snapshot of Kaspa's network health and infrastructure metrics. Key indicators include the current block rate (BPS), DAG width, tip count, peer count, mempool size, and DAA score. Together, these metrics paint a comprehensive picture of whether the network is operating normally or experiencing congestion, latency issues, or reduced participation.

Kaspa's unique BlockDAG architecture means that network state metrics behave differently than in traditional linear blockchains. Instead of a single chain tip, Kaspa maintains multiple parallel blocks that are merged through the GHOSTDAG protocol. This means metrics like tip count and DAG width have special significance — they reflect the degree of parallelism and the network's ability to process transactions concurrently without orphaning blocks.

For miners, node operators, and developers, this page serves as an operational dashboard. For traders and investors, it provides assurance that the underlying infrastructure supporting their holdings is functioning correctly. Network degradation — if it ever occurs — would be visible here before it manifests in price action or transaction delays.

How to use this data

A healthy Kaspa network at its current configuration should show a consistent 1 BPS (block per second) rate, a stable DAG width, and a tip count that fluctuates within a narrow range. The tip count specifically reflects network latency and miner geographic distribution — more tips indicate that blocks are being produced simultaneously by miners who haven't yet seen each other's blocks. A typical healthy tip count ranges from 15–25; significantly higher values may indicate network latency issues or a sudden influx of new miners.

Peer count serves as a decentralization metric. More connected peers means better network resilience, faster block propagation, and reduced risk of network partitions. A declining peer count over time could signal reduced interest in running full nodes, while spikes often correlate with network upgrades or community events that motivate new node deployments.

Monitor the mempool size to understand transaction demand. A consistently empty mempool means the network is comfortably handling all transaction volume — which is expected given Kaspa's high throughput. A growing mempool would indicate demand is temporarily exceeding capacity, though this is rare at current usage levels. The DAA score is Kaspa's monotonically increasing difficulty counter and serves as the network's logical clock.

How it's computed

All network status data is fetched directly from a Kaspa full node via its gRPC/RPC interface. The node exposes real-time state including the current virtual block's parent hashes (tips), connected peer count, mempool transaction count, and the latest DAA score. Our backend polls this data every few seconds and serves it through the API.

The block rate (BPS) is derived from observing the rate of new blocks added to the DAG over a rolling window. DAG width is calculated by counting how many blocks share the same DAA score level — blocks produced in parallel at roughly the same time. These derived metrics provide insight into the network's consensus efficiency.

Because this data is live and ephemeral (not historical), it represents the network's current state at the moment of viewing. The page auto-refreshes to keep metrics current. Historical trends for metrics like block rate and peer count are tracked separately in our time-series database for long-term analysis.