What is this?

This chart shows the total number of transactions confirmed on the Kaspa network per hour, split into two categories: standard transactions (user-initiated transfers, token operations, and contract interactions) and coinbase transactions (automatic block reward payouts). Together they represent the full transaction throughput of the network.

Kaspa's blockDAG architecture currently operates at 32 blocks per second (32 BPS), meaning the network produces approximately 115,200 blocks every hour. Each block contains exactly one coinbase transaction that pays the mining reward to the block producer. This results in a baseline of ~28,000–29,000 coinbase transactions per hour regardless of user activity — a direct reflection of the network's block production rate.

Standard transactions represent genuine economic activity: peer-to-peer KAS transfers, KRC-20 token operations, and any other user-initiated operations. Unlike coinbase transactions which are protocol-generated, standard transaction volume directly measures real network demand and adoption.

Understanding the two transaction types

Coinbase transactions are automatically created by the protocol for every block produced. Each DAG block has exactly one coinbase transaction with no inputs and a single output paying the block reward to the miner. At 32 BPS, the network generates ~2.76 million coinbase transactions per day. This number scales linearly with the block rate — when Kaspa increases to higher BPS in the future, the coinbase count will increase proportionally.

Standard (regular) transactions are user-initiated. They have one or more inputs (spending previous UTXOs) and one or more outputs (creating new UTXOs). These include KAS transfers between wallets, KRC-20 token mints/transfers, and any protocol-level operations. The standard transaction count is the true signal of network utility and adoption.

How to use this data

The coinbase layer acts as a stable baseline that reflects the network's block production rate. Focus on the standard transaction layer for adoption signals — sustained growth indicates increasing real-world usage, while spikes often correspond to token launches, NFT minting events, or new protocol deployments.

Comparing the ratio of standard to coinbase transactions reveals network utilization. A low ratio means blocks are mostly empty (low demand relative to capacity). A rising ratio indicates growing utilization of Kaspa's available throughput — an early indicator of potential fee pressure as the network approaches capacity.

The stacked view lets you see total network throughput (all transactions the DAG is processing) while still distinguishing organic demand from protocol overhead.

How it's computed

Transaction counts are sourced from the Kaspa network's archival indexer, which tracks every transaction accepted into the DAG. Transactions are bucketed into UTC hour windows based on the timestamp of the chain block that accepted them.

Coinbase transactions are identified by their subnetwork ID (0100000000000000000000000000000000000000) — a protocol-level field that unambiguously marks block reward payouts. Standard transactions use the native subnetwork (all zeros). This classification is deterministic and exact — there is no estimation or sampling involved.

Each transaction is counted exactly once at the point of acceptance into the virtual chain. Kaspa's GHOSTDAG consensus ensures that even though the same transaction may appear in multiple DAG blocks, it is accepted (finalized) exactly once when its containing block is ordered by the virtual chain.