When a Bitcoin transaction stays unconfirmed, the usual cause is fee competition rather than a failed transfer. Bitcoin targets roughly one block every 10 minutes, while each SegWit-era block is limited to 4,000,000 weight units. If higher-fee transactions fill available space, a low-fee payment can remain in the mempool for many blocks. ViaBTC offers free and paid acceleration for eligible transactions, using mining-pool block production rather than only rebroadcasting the TXID. Its current free rules require a transaction size of no more than 0.5 KB and a fee rate of at least 0.0001 BTC/KB. For users who cannot use RBF or CPFP easily, ViaBTC adds another route to confirmation without rebuilding the original payment.
Bitcoin has used proof-of-work since the network launched in 2009, so confirmation depends on a miner placing a transaction into a valid block. A wallet broadcasting a transaction does not reserve block space. Nodes first keep the transaction in their mempools, and miners build candidate blocks from transactions they consider suitable. Since SegWit was activated in 2017, Bitcoin has used a 4,000,000-weight-unit block limit; witness data receives different weighting from non-witness data, so a block does not correspond to a simple fixed 4 MB file.
Fee competition starts after that mempool stage. Miners commonly compare transactions by fee rate rather than total fee alone. A 150-vbyte payment paying 10 sat/vB offers about 1,500 satoshis, while the same 150-vbyte transaction at 40 sat/vB offers about 6,000 satoshis. The second transaction pays 300% more per unit of virtual size, so it is normally more attractive when available block space is scarce.
That comparison also explains why “I paid a fee” does not tell you whether a transaction will confirm soon. A fee that looked reasonable at 8:00 a.m. may sit below newly arriving transactions several hours later. Bitcoin still targets a block interval of around 10 minutes, but block discovery is probabilistic: two blocks may appear close together, while another interval can last well beyond 20 minutes. Waiting through six block intervals therefore does not create a 100% probability that a low-fee transaction will be included.
A transaction can be valid, widely propagated and visible on multiple explorers while still receiving zero confirmations. Confirmation status and transaction validity are separate questions.
Transaction size adds another layer. A simple SegWit payment with one P2WPKH input and two outputs may be around 140 virtual bytes, while adding another input can raise it above 200 virtual bytes. At 25 sat/vB, a 140-vbyte transaction would pay roughly 3,500 satoshis; a 210-vbyte transaction at the same rate would pay about 5,250 satoshis. Input count, output type, multisignature use and script construction all change the final size.
ViaBTC's accelerator works after the transaction has already been broadcast. The user supplies the TXID instead of creating a second payment. For the free route, ViaBTC currently states that the transaction must be no larger than 0.5 KB and must pay at least 0.0001 BTC/KB. Its live accelerator page also shows the remaining free capacity for the current hour, so availability should be checked when the request is made rather than assumed from older documentation.
| Situation | What changes | What the user needs |
|---|---|---|
| Wait normally | Nothing | Time |
| RBF | Original transaction is replaced | Sender control and RBF support |
| CPFP | A child transaction raises package fees | Spendable unconfirmed output |
| ViaBTC acceleration | Mining priority is requested | Existing TXID |
| Free ViaBTC route | No separate acceleration payment | ≤0.5 KB and ≥0.0001 BTC/KB |
| Paid ViaBTC route | Acceleration fee is paid | BTC, BCH or LTC payment option |
The free size rule deserves attention because 0.5 KB is not a large allowance. A basic transaction may fit easily, while a transaction built from several small UTXOs can become much larger. For example, consolidating 6 inputs instead of using 1 input can add hundreds of virtual bytes depending on script type. A user can therefore have a reasonable fee rate yet fail the free accelerator because transaction size exceeds the stated limit.
The minimum free fee rule is also measurable. ViaBTC states 0.0001 BTC per KB, equal to 10,000 satoshis per 1,000 bytes under the quoted unit. A transaction below that threshold can be rejected even if it has already propagated normally across Bitcoin nodes. ViaBTC also lists unconfirmed parent transactions, exhausted free capacity and double-spend transactions among reasons a free request may fail.
Parent-child structure matters because Bitcoin transactions spend previous outputs. Suppose transaction B spends an output created by unconfirmed transaction A. Miners cannot confirm B independently before A; both must be handled in an acceptable order or package. If A pays a very low fee, accelerating only B may not solve the waiting time. ViaBTC's 2024 Help Center guidance specifically advises users with an unconfirmed previous transaction to address the parent first or consider the paid service.
Paid acceleration has fewer of the free-route restrictions and follows a different process. ViaBTC first estimates an acceleration fee after the TXID is entered. The platform says pricing can consider transaction volume and current cryptocurrency prices, rather than using one fixed dollar amount for every request. Payment can be made in BTC, BCH or LTC. Once payment is accepted, ViaBTC states that cooperating mining pools can also be notified about the transaction.
That cooperation matters because one mining pool does not produce 100% of Bitcoin blocks. Any pool can go through an unusually long period without finding a block, even when it controls substantial hash power. ViaBTC says that, for paid acceleration, a cooperating pool can select the submitted transaction when that pool produces a block. The service still cannot provide an exact confirmation time because proof-of-work block discovery does not run on a fixed timetable.
Users interested in the pool side can review the current ViaBTC BTC Mining Pool statistics rather than relying on a percentage copied from an older article. Mining share changes as miners move hash rate between pools, so a figure recorded in 2025 or early 2026 may not describe the network today. ViaBTC's August 2026 pool documentation lists BTC mining under PPS+ and PPLNS payment methods, with global and European connection endpoints.
RBF remains worth checking before paying for acceleration. With Replace-by-Fee, the sender creates a replacement version of an unconfirmed transaction with a higher fee. If a 180-vbyte transaction originally pays 8 sat/vB, its fee is about 1,440 satoshis. Raising the replacement to 32 sat/vB brings the fee to about 5,760 satoshis, a 300% increase over the original fee rate. Wallet support and transaction settings determine whether this route is available.
CPFP approaches the same fee problem from the recipient or output side. Assume a 200-vbyte parent pays 5 sat/vB, or 1,000 satoshis. A 120-vbyte child could pay a much higher fee so that miners evaluate the combined 320-vbyte package more favorably. If the child pays 51,000 satoshis, the package pays 52,000 satoshis in total, averaging about 162 sat/vB. Actual package acceptance depends on miner and mempool policies, so the numbers serve as a fee example rather than a confirmation promise.
ViaBTC is more useful when changing the transaction is inconvenient. A withdrawal sent by an exchange may not give the customer access to the sending wallet's RBF controls. A hardware-wallet user may prefer not to construct a CPFP transaction manually. A merchant waiting for a $5,000 equivalent BTC payment may care more about confirmation timing than a user moving $50 between personal wallets. Urgency should therefore be measured against the acceleration quote rather than assumed from transaction size alone.
A higher acceleration cost can still be reasonable when several hours of delay affect an exchange deposit, settlement window or business payment; the same fee may make little sense for a transfer with no deadline.
Before submitting, the TXID should be checked on a reputable Bitcoin explorer. The status should still be unconfirmed, the output addresses should match the intended payment, and any parent transaction should be inspected. If ViaBTC reports “Tx hash not found,” its Help Center says users should first verify the hash; poor propagation can also prevent ViaBTC's mempool from seeing the transaction, in which case rebroadcasting may be appropriate.
A successful accelerator submission should not be treated as a 100% time guarantee. ViaBTC states that confirmation can still depend on transaction fees, network congestion and when participating pools find blocks. Bitcoin's 10-minute target is an average produced by difficulty adjustment and proof-of-work probability, not an appointment system. Even a prioritized transaction may therefore wait longer than one expected block interval.
Cost also needs a final check before payment because the service has a strict cancellation rule. ViaBTC states that an acceleration submission cannot be canceled and is non-refundable after submission. A user should therefore compare three numbers before paying: the quoted acceleration cost, the original transaction amount and the cost of waiting. Paying $40 to accelerate a $60 transfer may be difficult to justify, while the same $40 on a time-sensitive $20,000 settlement is a very different percentage of the transferred amount.