What is this?

This chart shows how much KAS was spent on transaction fees across the entire Kaspa network in each time bucket. Unlike the live rolling totals on the Fee Overview page, this view lets you zoom out and see how overall fee activity has changed over hours, days, or months.

Total fees combine two forces: how many transactions were confirmed and how much each transaction paid. A rise in total fees can mean more on-chain activity, higher fees per send, or both. On Kaspa, absolute fee amounts are usually small, so sustained increases often signal meaningful shifts in network usage rather than everyday noise.

Because Kaspa processes blocks at high throughput with ample capacity, total fees typically stay low compared to older blockchains. Spikes on this chart are worth attention — they often coincide with exchange movements, token activity bursts, or brief periods of higher demand for block inclusion.

How to use this data

Use the time range selector to switch between short-term detail and longer historical context. For recent congestion events, start with 24h or 48h (minute resolution). For weekly or monthly trends, use 7d or 30d (hourly resolution). For macro patterns, use 90d, 1y, or all (daily resolution).

Compare total fees with transaction count on the Accepted Transactions page. If total fees rise while standard transaction volume is flat, users may be paying more per send. If both rise together, the network is likely handling more economic activity overall.

Pair this chart with the Average Fee page when you want to separate volume effects from per-transaction cost. Total fees answer "how much did the network earn in fees?" while average fee answers "what did a typical sender pay?"

How it's computed

Each data point sums the exact fees paid by transactions accepted on-chain during that bucket. Fees are computed from resolved inputs and outputs (inputs minus outputs), not from block reward heuristics.

Bucket size depends on the selected range: minute buckets for ranges up to 48 hours, hourly buckets for medium ranges, and daily buckets for 90 days or longer. Values are stored in sompi and displayed in KAS with three decimal places.

Data is aggregated continuously as new blocks are processed by the analytics indexer. Partial coverage at the start of a range may appear when historical aggregation was not yet available — the notice above the chart indicates when that applies.