How many transactions can Bitcoin handle per second?

Bitcoin can process around 7 transactions per second, but with SegWit and layer-two solutions like the Lightning Network, scalability improves significantly.

Jul 06, 2025 at 04:28 am

Understanding Bitcoin's Transaction Capacity

Bitcoin, as the first and most well-known cryptocurrency, operates on a decentralized network that allows users to send and receive funds without intermediaries. One of the key metrics used to evaluate its performance is how many transactions it can handle per second (TPS). This number gives insight into the scalability and efficiency of the Bitcoin blockchain.

The theoretical maximum for Bitcoin's transaction throughput is around 7 transactions per second under standard conditions. However, this number is not fixed and can vary depending on several factors such as block size, transaction data volume, and network congestion. It’s important to note that actual TPS often falls below this ceiling due to practical limitations in how blocks are structured and processed.

Factors Affecting Bitcoin's Transactions Per Second

Several technical aspects influence how many transactions Bitcoin can process within a given timeframe. The block size limit, which currently stands at 1 megabyte (MB), plays a central role. Each block must contain all the transactions it confirms, and since the average size of a transaction varies based on inputs and outputs, the number of transactions per block can fluctuate.

Additionally, block time, or the average time it takes for a new block to be mined, is approximately 10 minutes. This means that regardless of how many transactions are waiting in the mempool (a holding area for unconfirmed transactions), they won't be confirmed until the next block is mined. These constraints collectively shape Bitcoin’s real-world TPS.

How Transaction Size Influences Throughput

Each Bitcoin transaction contains metadata such as sender information, receiver details, digital signatures, and change outputs. Larger transactions with more inputs require more space in a block, thus reducing the total number of transactions that can fit. For example, a simple transaction with one input and two outputs might take up about 250 bytes, allowing roughly 4 transactions per kilobyte, or about 4,000 transactions per MB.

If a block reaches the 1 MB limit, the number of transactions it can include depends heavily on their individual sizes. If each transaction averages 250 bytes, then one block can hold around 4,000 transactions. Given that a new block is mined every 10 minutes, this results in an average capacity of approximately 6.6 TPS.

Role of Segregated Witness (SegWit) in Increasing Capacity

The introduction of Segregated Witness (SegWit) in 2017 helped increase Bitcoin's transaction capacity without changing the block size limit directly. SegWit separates signature data from transaction data, thereby reducing the overall size of each transaction. This optimization effectively increases the number of transactions that can be included in a single block.

With SegWit adoption, the effective block size can reach up to almost 4 MB, depending on the proportion of SegWit transactions in a block. As a result, the potential TPS can rise to around 15–20 transactions per second, although actual figures depend on network usage patterns and SegWit adoption rates among wallet providers and exchanges.

Lightning Network: Scaling Beyond On-Chain Limits

To address Bitcoin’s limited on-chain transaction capacity, solutions like the Lightning Network have been developed. This second-layer protocol enables off-chain transactions between participants, only settling the final balances on the Bitcoin blockchain. By doing so, it significantly reduces the burden on the main chain and allows for millions of transactions per second across the network.

Users open payment channels with each other by locking funds on the blockchain. They can then conduct unlimited transactions within these channels without broadcasting them to the entire network. Only when the channel is closed does the final state get recorded on-chain. This method drastically improves scalability while keeping fees low and confirmation times fast.

---

Frequently Asked Questions (FAQs)

Q: Can Bitcoin ever handle thousands of transactions per second natively?

A: Native Bitcoin protocol improvements would be required to achieve such high throughput. Currently, layer-two solutions like the Lightning Network are the primary means of enabling higher transaction volumes without altering the base protocol.

Q: Why doesn’t Bitcoin just increase the block size to allow more transactions per second?

A: Raising the block size could compromise decentralization by increasing the storage and bandwidth requirements for running a full node. This trade-off makes larger blocks a contentious topic within the community.

Q: Do all Bitcoin transactions take the same amount of space in a block?

A: No, transaction size varies depending on the number of inputs and outputs involved. More complex transactions with multiple inputs consume more space, reducing the total number that can fit in a block.

Q: How does transaction fee affect confirmation speed if the TPS is limited?

A: When the network is congested and TPS is saturated, users must pay higher fees to incentivize miners to prioritize their transactions. Lower-fee transactions may remain in the mempool for extended periods.