ViaBTC TX Accelerator is useful when a valid Bitcoin transaction stays unconfirmed because its fee rate is below current miner preference. Bitcoin targets roughly one block every 10 minutes, so low-fee transactions can remain in the mempool across many block cycles when demand rises. ViaBTC accepts eligible free submissions up to 0.5 KB with a fee rate of at least 0.0001 BTC/KB, while paid acceleration supports broader cases. The service does not replace the transaction; it asks ViaBTC and cooperating pools to prioritize the existing TXID. It is especially useful when RBF is unavailable or CPFP would add another transaction.
A Bitcoin payment does not enter a block as soon as a wallet broadcasts it. It first competes with other unconfirmed transactions in the mempool, while miners normally prefer transactions that pay more per unit of block space. Bitcoin produces roughly 144 blocks in a 24-hour day when the long-term 10-minute target is maintained, so even several missed blocks can turn a routine transfer into a delay lasting 1 hour or more.
That fee competition matters more than the amount of BTC being sent. A $50 equivalent transfer can use more block space than a much larger payment if it contains many inputs, because miners evaluate transaction weight and fee rate rather than the dollar amount. A wallet that selected an adequate fee 30 minutes earlier can therefore fall behind newer transactions after demand for block space rises.
A transaction showing “unconfirmed” is usually still a valid network transaction. Confirmation depends on a miner selecting it for a block, not on the wallet displaying it successfully.
ViaBTC approaches the delay from the mining side rather than asking the sender to rebuild the payment. The user submits the existing TXID, and an accepted transaction receives higher inclusion priority within ViaBTC's mining process. For the free service, ViaBTC currently requires a transaction size of no more than 0.5 KB and a fee rate of at least 0.0001 BTC/KB.
Those limits explain why free acceleration cannot be treated as a universal replacement for normal fee selection. A transaction larger than 0.5 KB may be rejected even when its BTC amount is small, while a compact transaction can still fail if its original fee rate is below the stated minimum. ViaBTC also limits free capacity by hourly availability, so the live accelerator page should be checked instead of relying on an older published quota.
ViaBTC's 2024 help documentation referred to 20 free accelerations per hour, while the live interface can display a different current allowance. The current tool page is therefore the better reference for availability at the moment of submission. Eligibility rules and available capacity are separate: meeting the 0.5 KB and fee-rate requirements does not guarantee that a free slot will be open.
| Situation | What happens | Practical option |
|---|---|---|
| Fee rate is too low | Miners may keep selecting higher-paying transactions | RBF, CPFP, paid acceleration, or waiting |
| Size is above 0.5 KB | Free ViaBTC submission may be rejected | Paid service or wallet fee bump |
| Free hourly capacity is full | Eligible TXID cannot enter the free queue at that time | Retry later or use paid acceleration |
| Parent transaction is unconfirmed | Child transaction may also remain pending | Address the parent first |
| Transaction is already confirmed | No acceleration is needed | Wait for additional confirmations |
The relationship with Replace-by-Fee is also important. RBF lets a sender replace an unconfirmed payment with another version carrying a higher fee. Bitcoin Core documentation has supported opt-in RBF for years, and a wallet with proper fee-bump controls can often solve a slow transaction without using an external accelerator. RBF is normally most useful when the sender controls the wallet and can sign another version of the transaction.
ViaBTC is more useful when that control is missing. A transaction sent from a custodial service, older wallet, exchange withdrawal system, or wallet with limited fee controls may leave the user with only a TXID and no convenient way to raise the original fee. Acceleration works with the broadcast transaction rather than requiring a replacement signed with the sender's private keys.
CPFP takes another route. A recipient or other person controlling a spendable output creates a higher-fee child transaction that depends on the slow parent. Miners can evaluate the combined fee of both transactions. Bitcoin Core notes that RBF can use roughly 30% to 90% less additional block space than CPFP in relevant cases because RBF does not necessarily need another transaction.
That difference makes CPFP useful but less convenient for some wallets. The user needs a suitable unconfirmed output, the wallet must allow spending it, and the combined parent-child fee must be attractive enough. ViaBTC removes the need to build that second payment, although an unconfirmed parent can still prevent a free acceleration request from succeeding.
ViaBTC specifically lists an unconfirmed previous transaction as a reason a free request may fail. If transaction B spends an output from transaction A and transaction A has not confirmed, miners normally need to include A before or together with B. Accelerating only B does not remove that dependency, so checking the transaction ancestry before paying for service can prevent an unnecessary submission.
Checking the TXID on a public block explorer takes less than 1 minute and can show the fee rate, confirmation count, transaction size, inputs, outputs, and whether an earlier unconfirmed transaction is involved.
Paid acceleration provides another path when the free rules do not fit. ViaBTC lets users enter the TXID, receive an estimated acceleration charge, and pay using supported assets including BTC, BCH, or LTC. Its help material states that cooperative mining pools may also receive the acceleration request, increasing the number of participating miners able to include the transaction when they produce a block.
The payment should still be compared with the cost of waiting. A transfer delayed for 6 blocks is roughly 1 hour under Bitcoin's 10-minute target, but block discovery does not follow a fixed clock. Six blocks can arrive faster or slower than 60 minutes. Paying for acceleration makes more sense when the time cost exceeds the service charge than when a low-priority transfer can simply remain pending.
Bitcoin's miner economics help explain why transaction priority exists at all. The block subsidy was cut from 6.25 BTC to 3.125 BTC in April 2024, a 50% reduction at block 840,000. Transaction fees therefore remain part of miner revenue alongside the subsidy, giving miners an economic reason to select transactions that offer more fees for the block space they occupy.
Mining pools also receive transactions from their own mempools, so transaction availability matters as well as fee level. A valid payment that has not propagated properly may not be visible to every miner. ViaBTC's support documentation notes that a “Tx hash not found” message can occur when the transaction was poorly broadcast, and rebroadcasting it may be appropriate before attempting acceleration.
That check also separates a propagation problem from a fee problem. If several major block explorers can see the TXID but confirmation remains at 0 after multiple blocks, fee competition is a more likely explanation. If explorers cannot find the transaction at all, acceleration may not be the first step because miners cannot prioritize a transaction they have not received.
The service does not require a seed phrase or private key. A TXID is public blockchain data and can be viewed by anyone once the transaction propagates. No legitimate accelerator needs the 12-word or 24-word wallet recovery phrase to identify an existing transaction. A request for a recovery phrase is unrelated to normal transaction acceleration and should not be followed.
Users should also understand what “prioritized” does not promise. ViaBTC cannot state the exact minute a Bitcoin block will be found because proof-of-work block discovery is probabilistic. An accepted transaction may receive preferred treatment, but confirmation still depends on ViaBTC or a cooperating pool producing a suitable block and on the transaction remaining valid at that time.
One confirmation is also different from settlement depth. A transaction included in 1 block has one confirmation; after approximately 6 additional 10-minute block intervals, it can have substantially more confirmation depth. Exchanges and payment services choose their own deposit requirements, so accelerating the first confirmation does not make a platform ignore a policy requiring 2, 3, or 6 confirmations.
The connection with ViaBTC Crypto Mining is relevant because the accelerator is tied to mining infrastructure rather than being only a transaction-broadcast website. ViaBTC's current pool documentation lists PPS+ and PPLNS settlement methods, with a 4% fee applied to the PPS block-reward component under PPS+ and a 2% rate for the PPLNS transaction-fee component.
For someone deciding whether to submit a stuck transaction, five pieces of information are usually enough to inspect first:
-
Confirmation count: 0 confirms that the transaction is still pending.
-
Transaction size: free ViaBTC submissions currently require no more than 0.5 KB.
-
Fee rate: free acceleration currently requires at least 0.0001 BTC/KB.
-
RBF status: an enabled replacement option may allow the sender to increase the fee directly.
-
Parent status: an unconfirmed input can keep the current transaction waiting even after submission.
The choice changes with the ownership of the transaction. A sender using a modern self-custody wallet may prefer RBF because no third-party acceleration payment is needed. A recipient who controls an output may have CPFP available. A user with only a TXID from an exchange withdrawal may have neither option, making mining-pool acceleration more practical.
Transaction amount should not be used as the only measure. A 0.01 BTC transfer needed for an exchange deposit in the next hour may have greater time sensitivity than a 1 BTC transfer between two wallets controlled by the same owner. Checking urgency, fee rate, wallet controls, and transaction ancestry gives a more useful basis for choosing between waiting, RBF, CPFP, free acceleration, and paid acceleration.
ViaBTC also states that acceleration submissions cannot be canceled and the service is non-refundable after submission. Before paying, the TXID should therefore be checked character by character, the transaction should still show 0 confirmations, and the user should confirm that the wallet cannot solve the delay more cheaply. A 30-second verification can prevent payment for a transaction that confirmed naturally while the accelerator page was being opened.