Transactions per second (TPS) is a throughput measure: the number of transactions a network processes during a stated one-second interval. A TPS figure is meaningful only when the measurement explains what counts as a transaction, which layer and period it covers, and how failures or consensus activity are treated.
How TPS Is Calculated
A basic observed rate is transactions counted during a time window divided by the number of seconds in that window. Different dashboards and projects may count different things: successful user transactions, failed attempts, consensus votes, internal operations, or bundled actions. A test under maximum-capacity conditions is also different from an average observed rate on a live network.
For example, Solana’s official data dashboard separates total transactions from successful and failed non-vote transactions and vote transactions. That makes the counting method visible, but readers still need to select the metric and period that answer their question.
TPS Is Not the Same as Speed
Throughput is not the same as the time a user waits for a transaction, the time until it is considered final, or the fee paid. Ethereum’s documentation treats transaction throughput and faster finality as separate scaling goals. Comparisons should state which one they measure instead of presenting a single number as a complete measure of performance.
Layer 1 and Layer 2 Counts
A layer-2 system can execute many user transactions and send batches or proofs back to a layer-1 chain. A layer-1 TPS figure may not include each user action processed on a separate layer. When comparing ecosystems, identify whether the count covers the base chain, named layer-2 networks, or an aggregate, and avoid counting a batched action twice.
Common Misconceptions
“A larger TPS number always means a better network.” The number alone says little about decentralization, security, fees, reliability, user experience, or how the counted operations compare.
“Advertised maximum TPS is the rate users usually get.” A theoretical or benchmark result can differ from real-world activity and depends on test assumptions. Label the method and conditions.
“Transactions, instructions, and user actions are interchangeable.” One transaction can contain multiple instructions or be part of a batch. Counts across chains may therefore use different units.
Social Media Sentiment
- r/CryptoCurrency (2023 analysis thread): A user compared Solana’s reported transaction activity and argued that vote transactions should be separated from ordinary user activity. Replies discuss how to compare what chains count. This is one dated analysis thread, not a current performance measurement or a representative view of the whole community. Read the discussion about how TPS is counted.
Last updated: 2026-10
Related Terms
See Also
- Does Ethereum TPS Include Layer 2 Transactions?
- Are Layer 2 Networks Decentralized?
- What Is MEV? Ethereum Explained
- Swap crypto with ChangeNOW
Sources
- Solana, Network Data Dashboard — Separates total, successful non-vote, failed non-vote, and vote transaction metrics.
- Ethereum.org, “Scaling” — Distinguishes transaction throughput from faster finality and explains layer-2 rollups as a scaling approach.
- Solana Documentation, “Transactions” — Explains the transaction unit and how a transaction can contain one or more instructions.