Welcome to the second installment of our technical promenade—a journey through the foundational concepts that power blockchains like Alephium and shape the broader decentralized ecosystem. Whether you're evaluating Layer 1 platforms for your next dApp, exploring the crypto landscape out of curiosity, or deeply invested in decentralization, this guide is crafted with you in mind.
In our previous discussion, we unpacked block time and block size, two pivotal factors influencing blockchain throughput. Now, we dive deeper into one of the most cited—and often misunderstood—metrics in blockchain performance: Transactions Per Second (TPS).
While TPS appears straightforward, its interpretation varies widely across networks. Understanding how it's calculated, what it truly represents, and where its limitations lie is essential for making informed decisions in a space full of bold claims.
What Exactly Is TPS?
👉 Discover how real-world blockchain speed compares to the hype.
At its core, TPS (Transactions Per Second) measures how many transactions a blockchain can process within one second. The term originates from traditional database systems, where it serves as a benchmark for system efficiency. In blockchain, it’s frequently used to compare network speeds—especially by new Layer 1 and Layer 2 protocols touting high-performance capabilities.
However, “theoretical” TPS often diverges significantly from real-world throughput. Consider Visa: while it claims a peak capacity of 65,000 TPS, actual daily averages hover around 1,700 TPS. Similarly, many blockchains advertise lofty TPS figures during whitepaper launches, only to settle into much lower operational rates post-launch.
This gap underscores a crucial point: always treat advertised TPS with healthy skepticism.
How Is TPS Calculated?
The base formula for TPS is simple:
TPS = Number of Transactions per Block / Block Time (in seconds)But the devil lies in the details—especially in how different blockchains define and count “transactions.”
On Data-Centric Blockchains (e.g., Bitcoin)
Blockchains like Bitcoin and Zcash operate on a data-capacity model. Here, block size (in bytes) limits how many transactions can fit into a block.
To estimate TPS:
- Calculate transactions per block:
Block Size (bytes) / Average Transaction Size (bytes) - Divide by block time to get TPS.
Let’s apply this to Bitcoin:
- Average block size: ~1,249,169 bytes
- Average transaction size: ~632.53 bytes
- Block time: 600 seconds (10 minutes)
Transactions per block = 1,249,169 / 632.53 ≈ 1,975
TPS = 1,975 / 600 ≈ 3.29So, Bitcoin processes roughly 3.3 TPS under average conditions—consistent with historical data showing real-world throughput between 2 and 4 TPS.
Note: Real-world nuances like SegWit and virtual bytes (vB) affect actual capacity, but this calculation offers a solid approximation.
You can verify live metrics on explorers like mempool.space or Blockchair.
On Gas-Limited Blockchains (e.g., Ethereum, Alephium)
Here, computation cost, not data size, governs transaction inclusion. Users pay fees based on gas, a unit representing computational effort.
Key variables:
- Gas per transaction: Simple transfers cost 21,000 gas; complex smart contract interactions may exceed 1 million gas.
- Gas limit per block: Ethereum’s max is 30 million gas; target usage averages ~15 million.
If every transaction were a simple transfer:
Max transactions per block = 30,000,000 / 21,000 ≈ 1,428
Block time = ~14.5 seconds
Max TPS = 1,428 / 14.5 ≈ 98.5But reality is more complex:
- Most transactions consume more than 21,000 gas.
- Blocks rarely hit the 30M gas cap.
- Network congestion affects inclusion timing.
Thus, Ethereum’s average TPS stabilizes around 15, far below theoretical peaks.
Why TPS Comparisons Can Be Misleading
Not all "transactions" are created equal. Differences in definition and counting methods make cross-chain TPS comparisons tricky.
Solana: Success Rates and Vote Transactions
Solana reports high TPS—often over 2,000—but context matters:
- 10–15% of transactions fail, requiring adjustment for successful TPS.
- 25–30% are validator votes, not user transactions.
Therefore, usable throughput—non-vote, successful TPS—is significantly lower than headline numbers suggest.
Cardano: Batching and Multi-Transaction Blocks
Cardano uses advanced transaction batching. A single block may contain multiple logical transactions, but due to consensus constraints and design choices, its effective throughput remains low—around 2 TPS—despite technical capabilities for more.
The Hidden Factor: Finality
TPS measures throughput, not finality. A transaction may be confirmed quickly but take much longer to become irreversible.
For example:
- High TPS chains might rely on probabilistic finality (e.g., Nakamoto consensus).
- Others achieve near-instant finality via BFT-style mechanisms.
Thus, speed without certainty can be misleading. A fast transaction that isn’t finalized for minutes—or worse, can be reversed—is of limited utility in high-stakes applications like DeFi or payments.
Frequently Asked Questions (FAQ)
Q: Is higher TPS always better?
A: Not necessarily. High TPS at the cost of decentralization or security creates trade-offs. Sustainable scalability balances speed with network health.
Q: Why does Ethereum have lower TPS than newer chains?
A: Ethereum prioritizes decentralization and security. Its design favors broad node participation over raw speed—a deliberate trade-off.
Q: Can TPS increase over time?
A: Yes. Layer 2 rollups (e.g., Optimism, Arbitrum) boost effective TPS by processing transactions off-chain while inheriting Ethereum’s security.
Q: How do I check real-time TPS for a blockchain?
A: Use blockchain explorers like Blockchair, Etherscan, or mempool.space for live data on transactions per second and network congestion.
Q: Does TPS include failed transactions?
A: It depends. Some networks count all submitted transactions; others only include confirmed ones. Always check the methodology.
Q: What’s more important—TPS or finality?
A: Both matter. TPS reflects capacity; finality ensures trust. For mission-critical apps, finality often outweighs raw speed.
👉 See how next-gen blockchains are redefining transaction efficiency.
While TPS offers a useful snapshot of blockchain performance, it’s only one piece of the puzzle. Real-world usability depends on a network’s ability to deliver consistent throughput, rapid finality, and resilient decentralization.
As we’ve seen, comparing TPS across chains requires careful attention to definitions, success rates, and underlying architecture. Theoretical benchmarks are easy to market—but sustainable performance under load is what truly matters.
What’s Next: Understanding Finality
In the next chapter of our technical series, we’ll explore Time To Finality (TTF)—a critical but often overlooked metric that determines how quickly a transaction becomes irreversible. From probabilistic finality in proof-of-work chains to instant finality in BFT systems, we’ll break down how different blockchains secure trust.
Stay updated via official channels as we continue demystifying the tech behind decentralized networks.
👉 Learn how fast finality enables real-time blockchain applications.