bitunix

Cumulative Runes Transactions

Range
  • 1M1M
  • 3M3M
  • 6M6M
  • 1Y1Y
  • ALLALL
Scale
  • LinearLinear
  • LogLog
Latest
220.91M
2026-10-27 · 220,906,091
1D change
+0.23%
Prev. 220.41M
7D change
+1.61%
Prev. 217.41M
30D change
+6.63%
Prev. 207.17M
4Y percentile
100%
All history 100%
All-time high
220.91M
2026-10-27 · 0.00%
1Y range
110.43M – 220.91M
Since 2024-04-20
Loading data…

About this metric

What it measures

Cumulative Runes Transactions adds up the number of Bitcoin transactions identified as Runes-related from April 20, 2024 onward. The unit is transactions; this is a running total, not the number processed on a single day.

How to read it

A steeper line means more Runes-related transactions are being added each day; a flatter line means activity has slowed. The recorded total rose from about 80.49 million at the end of 2024 to 121.47 million at the end of 2025, showing that activity continued to accumulate beyond the initial launch.

A cumulative series normally rises even when daily demand weakens. Its all-time high and historical percentile therefore say little about current enthusiasm; compare additions over equal windows, alongside daily Runes counts and fees. Repeated activity by the same participants is counted again.

Frequency
Daily (UTC 00:00)
Asset
BTC
Type
Single value
Data since
2024-04-20
Latest data
2026-10-27
Data points
921

FAQ

How do I calculate daily Runes transactions from the cumulative chart?

Subtract the previous day's total from the current day's total. For a longer window, subtract the total at its start from the total at its end, allowing for any historical revisions.

Does a new cumulative high mean Runes activity is accelerating?

No. Any positive daily count raises the cumulative total. Acceleration requires larger daily additions, visible as an increasingly steep slope.

Does the total count Runes tokens or unique users?

Neither. It counts Bitcoin transactions classified as related to Runes. One participant can generate many transactions, and a transaction can involve more than one token operation.