Transactions per Second (TPS)
- 1M1M
- 3M3M
- 6M6M
- 1Y1Y
- ALLALL
- LinearLinear
- LogLog
About this metric
What it measures
Transactions per Second (TPS) divides the day's confirmed Bitcoin transaction count by 86,400 seconds, expressing average on-chain throughput in transactions per second. It measures observed daily activity rather than instantaneous processing speed or a fixed network capacity limit.
How to read it
Higher TPS means more transactions were confirmed on average that day; lower TPS means fewer. The recorded high was about 10.73 TPS on April 23, 2024. Changes reflect the mix and size of included transactions as well as how many blocks were found, so equal block-space usage can produce different TPS readings.
One transaction can batch several payments, while a protocol operation may produce a transaction without a conventional payment. The daily average smooths short bursts and does not include trades on exchange ledgers or activity settled outside the base chain. Read it with fees, block space and transaction size rather than as a user count or a live speed test.
- Frequency
- Daily (UTC 00:00)
- Asset
- BTC
- Category
- Transfers & Transactions
- Type
- Single value
- Data since
- 2009-01-12
- Latest data
- 2026-10-27
- Data points
- 6,498
FAQ
How do I convert daily transaction count into Bitcoin TPS?
Divide a full day's confirmed transaction count by 86,400. For example, 864,000 transactions in one day would average 10 TPS; this is an arithmetic example, not a capacity ceiling.
Why can observed Bitcoin TPS exceed seven?
Transactions do not have a fixed size, and the number of blocks found each day varies. Small transactions can fit in greater numbers, so seven TPS is not a universal hard limit on observed throughput.
Does Bitcoin TPS include Lightning payments or exchange trades?
It counts base-chain Bitcoin transactions only. Off-chain payments and internal exchange trades are absent unless they generate a transaction that settles on the Bitcoin blockchain.
