
Transactions Per Second, commonly referred to as TPS, is a metric that measures how many transactions a blockchain network can process and record within one second. TPS reflects the network’s throughput capacity and plays a crucial role in determining whether the network will experience congestion during peak periods.
TPS can be likened to the number of lanes on a highway: more lanes (higher TPS) allow more cars to pass through at the same time, reducing the likelihood of traffic jams. However, even with many lanes, if the road is not smooth (due to high network latency or widely distributed nodes), individual cars may still take a long time to reach their destination. This highlights the difference between TPS and latency.
TPS is important because it directly impacts user experience, transaction fees, and the feasibility of decentralized applications (dApps). Lower TPS increases the likelihood of congestion, forcing users to pay higher fees to prioritize their transactions and endure longer wait times.
For developers, the level of concurrency an application can handle is restricted by the network's TPS. For example, NFT minting events, blockchain-based gaming actions, or high-frequency trading on DEXs may face queuing, failed transactions, or skyrocketing fees if the target user base greatly exceeds the network's TPS. This can jeopardize business stability and reliability.
A common approach to estimate TPS is: TPS ≈ Average Number of Transactions per Block ÷ Block Time (in seconds). This formula is straightforward but may be influenced by transaction sizes, block packing strategies, and other factors.
For example:
It is important to note that TPS figures published by official sources or communities can vary depending on methodology: some report “theoretical peak” TPS, others report “sustained load,” and some may include “system or voting” transactions. These differences significantly impact the reported numbers.
TPS measures throughput—the number of transactions that can be processed simultaneously. Latency refers to the time it takes for a single transaction to be submitted, included in a block, and become visible. Finality describes when a transaction becomes irreversible on the network.
For example, a blockchain may have high TPS but require multiple rounds of confirmations before finality is achieved—users withdrawing funds to an exchange may still face delays. Another chain may have moderate TPS but short block times and rapid finality, resulting in a better experience for small payments. All three metrics are interrelated but serve different purposes and cannot substitute for each other.
TPS varies significantly across blockchains and depends on how it's measured. As of community data in 2025:
When assessing TPS figures, it’s critical to understand the methodology—whether it’s a theoretical peak or sustained load, whether system/voting transactions are included, and whether data comes from testnet or mainnet environments. These factors can drastically alter reported TPS values.
You can check current TPS data using blockchain explorers and community dashboards:
Step 1: Open the relevant blockchain explorer and review the “Blocks” or “Txns” pages to calculate the number of transactions over a set period. For example, on Etherscan you can observe total transactions in the last 10 minutes and divide by total block time to estimate TPS.
Step 2: Visit dedicated analytics dashboards. For Bitcoin, mempool.space provides throughput and congestion charts; for Solana, refer to official TPS metrics and community sites; for Ethereum and Layer2 networks, L2Beat’s Throughput page offers detailed data.
Step 3: Pay attention to measurement criteria. Check whether system transactions are included, whether figures represent peak or average values, and what sampling window is used. Numbers calculated using different methodologies are not directly comparable.
There are several main approaches to increasing TPS, each with trade-offs:
When depositing, withdrawing, or interacting with chains via Gate, TPS directly impacts transaction speed and fees. Low or congested TPS may require users to pay higher fees for faster inclusion, resulting in longer wait times.
For example, when selecting a network on Gate’s withdrawal page—such as ERC-20 (Ethereum Mainnet) vs. SOL (Solana)—differences in TPS and block times lead to noticeable variations in actual arrival times. During peak periods like NFT minting events or major project launches, insufficient TPS causes queuing and fee spikes. Users should expect longer waits during these times or opt for less congested networks.
For financial safety, always verify the stability and finality of your target network. Even with high TPS, unstable networks or rate limiting can still result in stuck or retried transactions.
When evaluating advertised TPS figures, focus on methodology and context:
TPS is a key indicator for evaluating blockchain throughput but must be considered alongside latency and finality while understanding different measurement methods. Before choosing a mainnet or Layer2 solution for your application, clarify your concurrency requirements and user experience goals. Continuously monitor real-world performance using explorers and dashboards. When using exchanges like Gate for deposits or withdrawals, consider both current TPS levels and network congestion when planning fees and timing—adjust your network selection or timing as needed. Approach advertised figures critically—focus on sustainable load capacity and security to strike the right balance between performance and decentralization.
Not necessarily. TPS only measures theoretical throughput; actual transaction speed also depends on network congestion, confirmation times, and other factors. A blockchain may advertise high TPS but still experience delays during busy periods because that figure represents ideal conditions. Always check the average transaction confirmation time rather than relying solely on advertised TPS.
There are several reasons: First, Gate transactions go through both platform processing and on-chain confirmation—not just dependent on blockchain TPS. Second, real-world throughput during congestion can fall far below theoretical figures. Third, your transaction may be queued behind others. For faster experience, try transacting during off-peak hours.
Take a rational approach to TPS claims. Many projects exaggerate their metrics—claiming speeds hundreds of times faster than Bitcoin or Ethereum—while real-world performance often differs significantly. Focus on actual transaction data instead of headline numbers; check daily active transaction volume and average confirmation times for a truer picture of performance.
Yes. For example, Bitcoin’s approximate 7-TPS limit helps maintain its strong security and high degree of decentralization—core aspects of its value proposition. Higher TPS is not always better; different chains make design trade-offs according to their priorities—some focus on throughput while others prioritize security. When choosing a blockchain, weigh security, decentralization, and transaction costs rather than simply pursuing high TPS.
It’s worth considering but not obsessing over. Gate optimizes routing and settlement internally—so even if a chain’s raw TPS is low, user experience remains relatively stable on the platform. Still, knowing your chosen chain’s TPS helps anticipate potential delays during peak periods; avoid large transactions during congested times for smoother processing.


