Free Bitcoin Transaction AcceleratorBTC stuck? Find out in seconds, free.

Every accelerator on the internet wants you to believe your transaction is in trouble, because worried people pay. We built StuckBTC to do the opposite job first. The scope reads your transaction from the public mempool, computes the effective fee rate including any unconfirmed parents, compares it against what the next block is actually accepting right now, and gives you a plain verdict. When the verdict says wait, you wait and keep your money. When it says act, we show you the cheapest honest fix and its exact cost in sats, next to what a paid accelerator would quote for the same job.

Blocks arrive on average every ten minutes, but the gap is random. Thirty or forty quiet minutes happen all the time and mean nothing is wrong. That single fact would save Bitcoin users a lot of accelerator fees if more sites said it out loud.

When you press Transmit, StuckBTC fetches your raw transaction and pushes it again to 20 independent Bitcoin nodes: public Esplora and mempool instances run by different operators in different countries, plus the push endpoints of the major block explorers. Each node answers for itself, and the scope shows you exactly what each one said. Accepted means the node took the transaction and is relaying it. Already held means the node knew it before we arrived, which is good news, your transaction has propagated. A node that is out of date or unreachable gets flagged in yellow or red, because a dead node cannot help you and we are not going to pretend it can.

What rebroadcasting can and cannot do

Honesty first: if all 20 nodes already hold your transaction, rebroadcasting it changes nothing, and no accelerator on earth can change that by resending it harder. Rebroadcasting earns its keep in two situations. First, when a wallet broadcast silently failed and the transaction never actually reached the network. Second, when the transaction sat unconfirmed for 14 days, got dropped from mempools, and needs to be reintroduced so miners can see it again. In both cases a wide push to many well connected nodes is exactly the right tool, and that is what this site does.

If your transaction was dropped and your wallet still shows it, you can paste the raw transaction hex into the box instead of the txid. We push the full transaction back into the mempool through all 20 nodes.

What the diagnosis checks

The old story about stuck BTC was congestion: too many transactions, not enough block space, fees spiking, and everyone below the spike waiting. That story is over for now. Across the last twelve months of blocks, the median block fee rate reached 5 sat/vB less than one percent of the time and never touched 10. The recommended fee has sat at 1 sat/vB for months. The mempool looks huge, around 44 blocks deep right now, but almost all of that queue is dust that will never compete with you.

Here is what actually happened. In September 2025, Bitcoin Core 29.1 lowered the default minimum relay fee from 1 sat/vB to 0.1 sat/vB. Wallets started letting people broadcast at economy rates near that floor. The result is a permanent standing queue. As measured today, 69 percent of all waiting transactions sit in the 0.1 to 0.2 sat/vB band, refilling as fast as it drains, and only 2.12 percent of the entire mempool pays more than 1 sat/vB.

So the modern stuck transaction is not a victim of congestion. It is a transaction priced at the relay floor, parked behind 44 blocks of identical fee dust, with no natural way out. Waiting rarely fixes it. Rebroadcasting does not fix it either, because every node already has it. What fixes it is raising the fee, and raising the fee usually costs a few hundred sats. The next section shows you how.

The other real causes we see, in order: an unconfirmed parent holding a child hostage, a broadcast that silently failed and never propagated, and a transaction dropped after the 14 day mempool expiry. The scope detects each of these and names the one you have, and we walk through all five in what to do when a transaction is stuck.

When the diagnosis says your fee genuinely is too low, you have two clean fixes, both of which you do from your own wallet, and both of which cost a tiny fraction of any paid acceleration service.

Replace By Fee, for the sender

RBF re signs the same payment with a higher fee. The new version replaces the old one in every mempool. Since Bitcoin Core 28 shipped full RBF, every unconfirmed transaction on the network is replaceable, so the old question of whether your transaction opted in no longer matters. The only question left is whether your wallet exposes the button.

Child Pays For Parent, for the receiver

CPFP is the fix when you are on the receiving end, or when you control a change output. You spend an output of the stuck transaction in a new transaction that pays a high fee. Miners weigh parent and child together as a package, so your child fee drags the parent into a block with it.

If your coins came from an exchange withdrawal, you cannot RBF it yourself because the exchange signed the transaction. Your options are CPFP on your receiving output once it appears, asking the exchange support to bump, or simply waiting. This is also the one honest scenario where a paid pool accelerator can make sense, because nobody in the transaction can bump the fee.

We measured this instead of guessing. In the public acceleration records we sampled from the largest pool backed accelerator, the median accelerated transaction already paid 2 sat/vB, comfortably above the next block floor, and the median fee delta bought was about 2,500 sats. The median wait to confirmation after paying was around 24 minutes, roughly two and a half blocks, which is close to what those transactions would likely have seen anyway.

None of this means paid pool acceleration never works. The big one is backed by pools that really do mine most blocks, and paid transactions do get mined. It means the price is usually many multiples of the real shortfall, and a meaningful share of buyers pay for transactions that needed nothing. That is the part no accelerator will tell you, so we do.

We wrote the whole investigation up separately, with the lifetime records, the live quotes we pulled, and the hashrate recomputed from block data: do Bitcoin transaction accelerators actually work?

This corner of the internet has a scam problem, and even the legitimate operators admit it. Before you trust any acceleration site with anything, run it against this list.

Useful independent references: mempool.space for live mempool data, Bitcoin Optech on out of band fees for why paying miners off chain worries protocol developers, and the Bitcoin wiki on RBF.

Nothing hidden. These are the public Bitcoin nodes and explorer push endpoints StuckBTC relays through. Different operators, different countries, different software stacks. When one goes stale or dies, the scope shows it flagged instead of faking a success, and we rotate it out.

SatoshiLabs runs five of these Blockbook servers, btc1 through btc5. We use one. Counting all five would make the list look longer without adding a single independent operator, and a padded number is exactly the kind of thing this site exists to call out.