Chapter 04 — live telemetry

Mainnet,
as it is

Every number on this page is read from the public Kaspa REST API and refreshed every twenty seconds. Nothing is cached longer than fifteen seconds at the edge, nothing is interpolated, and where an upstream endpoint is unavailable the tile says so rather than showing a stale figure.

connecting

At a glance

Poll interval20 seconds

Edge cache15s + stale-while-revalidate

Sourceapi.kaspa.org

Node version—

Node synced—

Network hashrate

Difficulty

Retargets continuously, not on a 2016-block schedule

Spot price

USD

Virtual DAA score

Difficulty-adjusted block count — what hardfork activations are keyed to

Virtual chain blue score

Accumulated blue-set weight along the selected chain

Total blocks

Every block ever accepted, blue and red alike

DAG frontierawaiting tip data

The tip count above is live from mainnet. The animation is a rendering of what ten blocks per second looks like at that concurrency — it is not a stream of the actual blocks, and it is labelled that way everywhere on this site.

Mempool

transactions

A shallow mempool at 10 BPS is the expected state, not a sign of low usage

Tips at the frontier

Blocks not yet referenced by any other block

Next reward reduction

--d --:--:--

Current reward—

Drops to—

Supply

Circulating—

Reported max supply—

Policy cap28,704,035,605 KAS

Issued—

Remaining to mine—

Kaspa month—

Poll status

Last successful fetch—

Age—

Endpoints degraded—

Node version—

Node synced—

Client statusloading

Polling pauses automatically while this tab is in the background and resumes the moment you come back, so leaving the monitor open does not hammer the upstream API.

How to read this page

Numbers without context are decoration

§ What each figure actually tells you

Dashboards invite the assumption that every metric is a scoreboard. Most of these are not. Here is what each one is genuinely evidence of, and what it is not.

Hashrate

Evidence of

The cost of rewriting recent history. Higher means an attacker needs more hardware and more electricity to reorganise the DAG.

Not evidence of

Not a demand signal, and not comparable across different hash functions. Comparing a kHeavyHash figure to a SHA-256 figure is meaningless.

Difficulty

Evidence of

The target the network has set so that blocks arrive every 100 ms at the current hashrate. It tracks hashrate closely because it retargets continuously.

Not evidence of

Not an independent metric. If you already know hashrate, difficulty tells you very little extra.

DAA score

Evidence of

A difficulty-adjusted count of blocks. This is the clock hardfork activations are keyed to — Toccata activated at DAA 474,165,565, not at a wall-clock time.

Not evidence of

Not a block height in the Bitcoin sense. In a DAG there is no single canonical height.

Tip count

Evidence of

How wide the frontier currently is — how many blocks exist that nothing has referenced yet. Concurrency, made visible.

Not evidence of

Not a health warning. Multiple tips is the normal, intended state of a blockDAG at 10 blocks per second.

Mempool depth

Evidence of

How many transactions are waiting. At this block rate a near-empty mempool means capacity comfortably exceeds current demand.

Not evidence of

Not proof of low adoption, and not proof of high adoption when it fills. Fee market conditions matter more than the raw count.

Block reward

Evidence of

The current subsidy per block, which steps down every Kaspa month. Multiply by ten for issuance per second.

Not evidence of

Not miner revenue. Revenue is subsidy plus fees, minus pool cuts, and fees are the part that has to grow over time.

Turn hashrate into a cost model Query the API yourself

Chapter 04 — live telemetry

Mainnet,
as it is

connecting

At a glance

Poll interval20 seconds

Edge cache15s + stale-while-revalidate

Sourceapi.kaspa.org

Node version—

Node synced—

Network hashrate

Difficulty

Retargets continuously, not on a 2016-block schedule

Spot price

USD

Virtual DAA score

Difficulty-adjusted block count — what hardfork activations are keyed to

Virtual chain blue score

Accumulated blue-set weight along the selected chain

Total blocks

Every block ever accepted, blue and red alike

DAG frontierawaiting tip data

Mempool

transactions

A shallow mempool at 10 BPS is the expected state, not a sign of low usage

Tips at the frontier

Blocks not yet referenced by any other block

Next reward reduction

--d --:--:--

Current reward—

Drops to—

Supply

Circulating—

Reported max supply—

Policy cap28,704,035,605 KAS

Issued—

Remaining to mine—

Kaspa month—

Poll status

Last successful fetch—

Age—

Endpoints degraded—

Node version—

Node synced—

Client statusloading

Polling pauses automatically while this tab is in the background and resumes the moment you come back, so leaving the monitor open does not hammer the upstream API.

How to read this page

Numbers without context are decoration

§ What each figure actually tells you

Dashboards invite the assumption that every metric is a scoreboard. Most of these are not. Here is what each one is genuinely evidence of, and what it is not.

Hashrate

Evidence of

The cost of rewriting recent history. Higher means an attacker needs more hardware and more electricity to reorganise the DAG.

Not evidence of

Not a demand signal, and not comparable across different hash functions. Comparing a kHeavyHash figure to a SHA-256 figure is meaningless.

Difficulty

Evidence of

The target the network has set so that blocks arrive every 100 ms at the current hashrate. It tracks hashrate closely because it retargets continuously.

Not evidence of

Not an independent metric. If you already know hashrate, difficulty tells you very little extra.

DAA score

Evidence of

A difficulty-adjusted count of blocks. This is the clock hardfork activations are keyed to — Toccata activated at DAA 474,165,565, not at a wall-clock time.

Not evidence of

Not a block height in the Bitcoin sense. In a DAG there is no single canonical height.

Tip count

Evidence of

How wide the frontier currently is — how many blocks exist that nothing has referenced yet. Concurrency, made visible.

Not evidence of

Not a health warning. Multiple tips is the normal, intended state of a blockDAG at 10 blocks per second.

Mempool depth

Evidence of

How many transactions are waiting. At this block rate a near-empty mempool means capacity comfortably exceeds current demand.

Not evidence of

Not proof of low adoption, and not proof of high adoption when it fills. Fee market conditions matter more than the raw count.

Block reward

Evidence of

The current subsidy per block, which steps down every Kaspa month. Multiply by ten for issuance per second.

Not evidence of

Not miner revenue. Revenue is subsidy plus fees, minus pool cuts, and fees are the part that has to grow over time.

Turn hashrate into a cost model Query the API yourself