The Kaspa network handles 10 BPS without breaking a sweat. The infrastructure that indexes and serves that data to wallets and exchanges is being upgraded to keep pace.
The Kaspa network — consensus, block production, transaction finality — is running at full capacity with zero issues. It was purpose-built for this throughput.
The explorer is a separate system that reads, indexes, and serves blockchain data to wallets, exchanges, and block explorer websites. It's this layer that struggles during sustained high traffic.
When someone says "Kaspa is slow" — what they're actually experiencing is the explorer falling behind, not the network.
Every transaction passes through these stages before it appears in your wallet.
10 blocks per second. Over 2,000 TPS. Operating exactly as designed.
Reads every block and organizes data for lookups. Pushed to its limits at sustained peak throughput.
Writing thousands of records per second while simultaneously serving read queries. This is where the pipeline breaks down.
Serves data to wallets and exchanges. Response times increase when the database is saturated.
Stale balances, delayed confirmations, missing recent transactions. The data exists — it hasn't been served yet.
These are display-layer delays — not network failures. Your transaction is confirmed on the DAG.
Wallet shows an old number after a send or receive. Resolves as the indexer catches up.
It's on the DAG permanently. The explorer hasn't indexed it yet.
The network confirmed it. The exchange's explorer query is lagging behind.
The explorer website shows blocks from minutes ago during peak load.
Kaspa's consensus layer was engineered from scratch for massive throughput. The explorer was built separately by community developers using general-purpose database tooling.
Adoption has grown to the point where the network regularly operates at speeds the explorer infrastructure was never designed for.
The team is aware and actively shipping fixes. Multiple optimizations have already been deployed, with more in progress.
No. Funds are secured by Kaspa's consensus layer, which is fully operational. The explorer is a read-only display layer — it has no effect on your balance or transaction finality.
If the network accepted it, yes. It's on the DAG permanently. The explorer may take additional time to display it during peak traffic.
No. Every high-throughput blockchain deals with explorer lag at peak — Bitcoin, Ethereum, Solana included. Kaspa's base layer is fast enough that the gap is more visible.
No. Infrastructure upgrades are being built in phases to stay ahead of throughput increases through 32 BPS and beyond.
No. Every transaction on the DAG is permanent and public. This only affects how quickly indexed data becomes searchable through the explorer.
Use kaspa-ng — it connects directly to a node via wRPC, bypassing the explorer entirely. Real-time balances with no dependency on the indexing pipeline.
Run a node. More nodes means more direct connection options for wallets and exchanges. The indexer and API server are open-source if you want to contribute.
Kaspa • March 2026