Use Kaspalytics for on-chain history and supply structure, an explorer for a single transaction or address, and a market site for price. Kaspalytics is the deepest free chart set on Kaspa, covering supply aging, exchange holdings, address buckets and covenant activity. For one specific transaction, address or block, use explorer.kaspa.org or the open REST API behind it. For KRC-20 tokens use kas.fyi. For price, volume and exchange data, any market site will do. Nobody is wrong when the numbers differ, they are usually answering different questions.
| Source | Best for | Refresh | Access |
|---|---|---|---|
| Kaspalytics | on-chain history and supply structure, hash rate, difficulty, active addresses, fees, supply aging and HODL waves, exchange holdings, address balance buckets, script types and covenant activity | network and fee views in seconds, supply and address aging about once a day around 00:00 UTC | free, no account |
| kaspa.stream | watching the chain move block by block, blocks and transactions as they land, top addresses, miner and node metrics | continuous | free, no account |
| explorer.kaspa.org | one specific transaction, address or block, with the same explorer available for the testnets | continuous | free, no account |
| api.kaspa.org | pulling that same data yourself in code, documented as an OpenAPI page you can click through | continuous | free, no key |
| kas.fyi | KRC-20 tokens, with a page per token | continuous | site free, the developer platform at docs.kas.fyi uses API keys and paid plans |
| KasLens | the market side, price across exchanges, volume, order book heatmap, a KRC-20 dashboard | continuous | free, no account |
| KASLIVE | a continuous monitoring terminal, including large address movement, a mining calculator and an attack cost estimate | continuous | free, no account |
| DeFiLlama | money inside the layer 2s, meaning TVL and volume for Kasplex and Igra and the apps on them | continuous | free, no account |
| Kaspa Pulse | one weekly reading of the numbers that carry weight, with the definition printed next to each one | every Monday | free, no account |
Two things are worth saying plainly. First, almost all of this is free and made by people in this community for nothing, which is not normal for a chain this size. Second, none of these tools is trying to mislead anyone. When two of them disagree, the cause is nearly always a definition, not an error.
This is the one that catches people out most often, so it is worth walking through with the real numbers rather than in the abstract. In August 2026 a running counter on one site was showing somewhere around 11 transactions per second while our own dashboard was publishing 2.34 for the same week. Both figures are defensible. They count different things.
We take the accepted transactions for a full day, standard transactions plus coinbase transactions, and divide by the 86,400 seconds in that day. Accepted matters, because Kaspa produces around ten blocks a second in parallel, so the same transaction can appear in more than one block before the DAG settles which of them counts. Counting accepted transactions counts each one once, after that has been decided. Dividing by a whole day means we publish an average across quiet nights and busy afternoons alike, not a moment.
A running counter is built to show flow, so it counts what is streaming past as it happens, which includes the coinbase transaction that every one of those ten blocks a second carries with it. We cannot see anyone else's code and we do not claim to know exactly how another site counts. What we can say is that a per-second reading and a per-day accepted average are different measurements, and that the gap between them on Kaspa is structural, not a bug in either.
We are a source on this list, so the same standard applies to us. The weekly figures on the dashboard come from Kaspalytics for supply aging, exchange holdings, active addresses and accepted transaction counts, from api.kaspa.org where we count something ourselves transaction by transaction, and from DeFiLlama for layer 2 value. Hash rate and difficulty are cross-checked against more than one source before they go out.
Where we cannot verify a number, we print a dash instead of a guess. That is why the dashboard occasionally shows blanks while other sites show a figure for the same tile. A dash means we could not stand behind it that week, and we would rather be visibly incomplete than quietly wrong. When we do make a claim about what a wallet did, we counted every transaction ourselves and we report the movement, never the motive.
Kaspalytics is a free on-chain analytics site for Kaspa. It publishes chart sets for mining, meaning hash rate and difficulty, for transactions, meaning counts, active addresses, fees, script types and covenant activity, and for supply, meaning exchange holdings, supply aging and HODL waves, address balance buckets and realized price. It needs no account. Network and fee views refresh within seconds, while supply aging and address balance views update about once a day around 00:00 UTC.
Yes. The REST API behind the public Kaspa explorer is available at api.kaspa.org with a documentation page you can click through, and it needs no key. Equivalent endpoints exist for the testnets. Separately, kas.fyi runs a developer platform at docs.kas.fyi that uses API keys and paid plans for higher volume access.
Because they measure different things. Kaspa produces roughly ten blocks per second in parallel, and every block carries a coinbase transaction, so a running counter showing raw flow will read far higher than a figure built from accepted transactions. Kaspa Pulse divides the accepted transactions of a full day, standard plus coinbase, by 86,400 seconds, which counts each transaction once and averages across the whole day. A per second reading and a per day accepted average are both valid, and neither is an error.
For a single transaction, address or block, explorer.kaspa.org is the straightforward choice and covers the testnets too. For watching blocks and transactions arrive block by block, along with miner and node metrics, kaspa.stream is built for that view. For KRC-20 tokens, kas.fyi has a page per token.
Supply aging, exchange holdings, active addresses and accepted transaction counts come from Kaspalytics. Anything counted transaction by transaction, such as the movement out of the largest wallet on the chain, is counted from api.kaspa.org directly. Layer 2 value comes from DeFiLlama. Hash rate and difficulty are cross checked against more than one source. Where a number cannot be verified, the dashboard prints a dash instead of an estimate.
Kaspalytics publishes an exchange holdings chart, which sums the balances of addresses identified as belonging to exchanges. Read it as a movement signal rather than a certainty. Address labelling is inference, a deposit to an exchange is not proof of a sale, and a withdrawal from one is not proof of a purchase.
follow kaspa pulse