Solutions for stuck transactions

[jillscarbrough]

Many members here, asking "Please Help me, my transaction stuck!" or something like that.

First, what makes your transactions go stuck?
-This is a part of 10 minutes blocks.
-The network is often running at over capacity

Solutions:
-Check block explorer before sending your bitcoin. Bitcoin block time is 10 minute, and blcokchain will maintain the block time to keep 2016 block solved in 14 days. It means, after poor block, we will find faster block.
-Use higher fee, so you'll on priority.
-Use Transaction Accelerator.

Ex.
Let's are using viabtc.
Open https://pool.viabtc.com/tools/txaccelerator/ , Input your tx id, enter the Captcha and Submit.

Good Luck!

[racquemis]

You forgot to mention the most important thing.... set enough fees.

[jillscarbrough]

You forgot to mention the most important thing.... set enough fees.

Solutions:
-Use higher fee, so you'll on priority.

[aleksej996]

Using RBF is pretty good way to insure your transaction doesn't get stuck if you are unsure if the fee is enough.

But if your transaction is already stuck other then using transaction accelerators you can easily just use CPFP method.
Of course for CPFP you need to control the receiving address in the transaction or be able to ask the receiver to use CPFP to get the transaction confirmed.

[NeuroticFish]

Many members here, asking "Please Help me, my transaction stuck!" or something like that.

The main answer for all questions is to search. There are already very good answers and threads, just google for: stuck transaction site:bitcointalk.org
The first result is this: https://bitcointalk.org/index.php?topic=1802212.0
It cointains a lot more tips.

[jillscarbrough]

The main answer for all questions is to search. There are already very good answers and threads, just google for: stuck transaction site:bitcointalk.org
The first result is this: https://bitcointalk.org/index.php?topic=1802212.0
It cointains a lot more tips.

That's right. Many people only focus on their problem. They even didn't try to find solutions, just asking and waiting for someone to help him.

[onrise]

The main answer for all questions is to search. There are already very good answers and threads, just google for: stuck transaction site:bitcointalk.org
The first result is this: https://bitcointalk.org/index.php?topic=1802212.0
It cointains a lot more tips.

That's right. Many people only focus on their problem. They even didn't try to find solutions, just asking and waiting for someone to help him.

What I have understood is that as btc price is rising the network fees are automatically getting costlier and people who have to transfer fractional btc to friends/making payments etc cannot afford that fees and due to which set the low satoshi as the fees and this gets stuck for a longer time.

Providing the accelerated link will help as people can themselves use this link and do it rather than waiting for others to accelerate their transactions.

[NeuroticFish]

What I have understood is that as btc price is rising the network fees are automatically getting costlier and people who have to transfer fractional btc to friends/making payments etc cannot afford that fees and due to which set the low satoshi as the fees and this gets stuck for a longer time.

Providing the accelerated link will help as people can themselves use this link and do it rather than waiting for others to accelerate their transactions.

The cost depends on Bitcoin price, the size of the mempool (how busy the network is), the size of transactions (it's more expensive to transfer a truck of pennies than a couple of $100 bills)...
If everybody can easily accelerate his own transaction for free (or very cheap), everybody will do that and the "accelerated" transactions will be too many, leading to the point where acceleration means almost nothing.
Already ViaBTC accelerator is almost unreachable. More will be posted and still working, they'll have the same fate.

The solutions are: pay the right fee or wait and send the money when it's not as busy. Optimize. Use accelerators only for desperate cases.

[mocacinno]

Solutions:
-Check block explorer before sending your bitcoin. Bitcoin block time is 10 minute, and blcokchain will maintain the block time to keep 2016 block solved in 14 days. It means, after poor block, we will find faster block.

I would like to comment on your first sollution: it's not technically correct...
The average time between 2 blocks will be 10 minutes. If more ASIC's get turned on (more hashrate enters the network), the average time between 2 blocks declines, and vice-versa.
Every 2016 blocks, the difficulty gets adjusted, so the average time between 2 blocks is 10 minutes once again, however, there is no guarantee the average time between 2 blocks will still be 10 minutes a couple minutes after the last diff adjustment.

If the time between the block at height a and a+1 is, for example, 20 minutes, there is no guarantee whatsoever that the time between block at height a+1 and a+2 will be less than 10 minutes...

Also, it's possible there are hundreds of Mb of unconfired transactions in the mempool that all have a higher fee than your transaction, so even if the blocks were faster, you'd still need to outbid them... So there is no need to look at a block explorer and broadcast your transaction after you see that the time between two blocks was bigger than 10 minutes, it simply does not matter...

[bob123]

Of course for CPFP you need to control the receiving address in the transaction or be able to ask the receiver to use CPFP to get the transaction confirmed.

If the input of the transaction is not fully going to the reciever (which i think applies to the majority of transactions) a change address is created.
An CPFP can be executed with any output and therefore also with the change address. This way a sender also can accelerate the TX without having to rely on the recipient.
Replace-by-fee is still the simpliest way of getting a stuck transaction confirmed. Just need to set the RBF flag each TX to let the nodes know this fee might get adjusted later on.
Sadly only a handful of wallets (e.g. electrum) provide the function to set this flag.

[rawedok]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

Thanks a lot & Cheers!!

[mocacinno]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

Thanks a lot & Cheers!!

It's actually quite hard to explain this in detail... This is why i made a wizard a long time ago...
1) surf to http://www.mocacinno.com/page/feechecker
2) enter the transactionid of the stuck transaction
3) near the bottom of the page, you'll see a section called CPFP
4) this section has (in your case) 2 buttons: one creating a CPFP with the unspent output that went to the other party, one creating a CPFP with the unspent output that went to your change address. Obviously, you need to select the button creating a CPFP with the unspent output to your change address (since you don't posses the other party's private keys).
5) double check, tripple check, quadripple check the transaction, i would suggest not to use the decoder on my site alone, but also run the raw transaction trough a thirth party raw transaction decoder like https://blockchain.info/decode-tx
6) if you're happy with the end result, you need to sign the raw transaction... Open the debug console again, and type "signrawtransaction [therawtransaction". The output will be a signed, raw transaction
7) try a different raw transaction decoder, check for the 100th time
if you're happy with the end result, open your debug console and type "sendrawtransaction [rawsignedtransaction]"

[bob123]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

For a CPFP in electrum:

• Find the change address of your transaction stuck
• In electrum goto Adresses -> Change
• Select your address from 1) with right click and pick 'spend from'
• Now set a fee which is high enough to cover the fee of both transactions (goto https://bitcoinfees.earn.com/, for 2 TX's: double the recommended fee)
• Broadcast the TX

If electrum gives you an error you have to push/broadcast the TX by yourself. But usually this doesn't give an error.

[rawedok]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

Thanks a lot & Cheers!!

It's actually quite hard to explain this in detail... This is why i made a wizard a long time ago...
1) surf to http://www.mocacinno.com/page/feechecker
2) enter the transactionid of the stuck transaction
3) near the bottom of the page, you'll see a section called CPFP
4) this section has (in your case) 2 buttons: one creating a CPFP with the unspent output that went to the other party, one creating a CPFP with the unspent output that went to your change address. Obviously, you need to select the button creating a CPFP with the unspent output to your change address (since you don't posses the other party's private keys).
5) double check, tripple check, quadripple check the transaction, i would suggest not to use the decoder on my site alone, but also run the raw transaction trough a thirth party raw transaction decoder like https://blockchain.info/decode-tx
6) if you're happy with the end result, you need to sign the raw transaction... Open the debug console again, and type "signrawtransaction [therawtransaction". The output will be a signed, raw transaction
7) try a different raw transaction decoder, check for the 100th time
if you're happy with the end result, open your debug console and type "sendrawtransaction [rawsignedtransaction]"

That is really nice of you, thanks! I get the steps I have to do but I don't have the neccessary knowledge to fully comprehend what is happening. With checking the transaction you mean the addresses displayed in the raw transaction decoder?

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

For a CPFP in electrum:

• Find the change address of your transaction stuck
• In electrum goto Adresses -> Change
• Select your address from 1) with right click and pick 'spend from'
• Now set a fee which is high enough to cover the fee of both transactions (goto https://bitcoinfees.earn.com/, for 2 TX's: double the recommended fee)
• Broadcast the TX

If electrum gives you an error you have to push/broadcast the TX by yourself. But usually this doesn't give an error.

Unfortunately it's bitcoin core, but thanks!

[mocacinno]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

Thanks a lot & Cheers!!

It's actually quite hard to explain this in detail... This is why i made a wizard a long time ago...
1) surf to http://www.mocacinno.com/page/feechecker
2) enter the transactionid of the stuck transaction
3) near the bottom of the page, you'll see a section called CPFP
4) this section has (in your case) 2 buttons: one creating a CPFP with the unspent output that went to the other party, one creating a CPFP with the unspent output that went to your change address. Obviously, you need to select the button creating a CPFP with the unspent output to your change address (since you don't posses the other party's private keys).
5) double check, tripple check, quadripple check the transaction, i would suggest not to use the decoder on my site alone, but also run the raw transaction trough a thirth party raw transaction decoder like https://blockchain.info/decode-tx
6) if you're happy with the end result, you need to sign the raw transaction... Open the debug console again, and type "signrawtransaction [therawtransaction". The output will be a signed, raw transaction
7) try a different raw transaction decoder, check for the 100th time
if you're happy with the end result, open your debug console and type "sendrawtransaction [rawsignedtransaction]"

That is really nice of you, thanks! I get the steps I have to do but I don't have the neccessary knowledge to fully comprehend what is happening. With checking the transaction you mean the addresses displayed in the raw transaction decoder?

well, you need to double check that the input (vin) is indeed the unconfirmed unspent output to your change address, then you need to double check that the address being funded by the output (vout) is indeed your address, and that the value is indeed the value of the input minus a rather big fee. You can either trust my wizard and assume that the difference between inputs and outputs is suffienctly large as a fee, or you can manually re-calculate the fee... It's up to you

[jillscarbrough]

I would like to comment on your first sollution: it's not technically correct...
The average time between 2 blocks will be 10 minutes. If more ASIC's get turned on (more hashrate enters the network), the average time between 2 blocks declines, and vice-versa.
Every 2016 blocks, the difficulty gets adjusted, so the average time between 2 blocks is 10 minutes once again, however, there is no guarantee the average time between 2 blocks will still be 10 minutes a couple minutes after the last diff adjustment.

If the time between the block at height a and a+1 is, for example, 20 minutes, there is no guarantee whatsoever that the time between block at height a+1 and a+2 will be less than 10 minutes...

Also, it's possible there are hundreds of Mb of unconfired transactions in the mempool that all have a higher fee than your transaction, so even if the blocks were faster, you'd still need to outbid them... So there is no need to look at a block explorer and broadcast your transaction after you see that the time between two blocks was bigger than 10 minutes, it simply does not matter...

Yeah, it isn't a technical as well, point 1 and 2 are correlated. Beside a small size transactions, the other main concept of cryptocurrency is, "fast send and receive transactions." Yes, Technically No guarantees after poor block we will find a fast block, in fact since 2010 till now average block time still constant: https://bitinfocharts.com/comparison/bitcoin-confirmationtime.html

I mean point 1 an additional option to approaching the new block. So we can reduce some minute. Point 2 is the key to this problems. And the 3rd point is an additional option for point 2 (in case).

Thank you for your correction!

[rawedok]

mocacinno, I wrote you a pm before. Unfortunately I can't write more than 1 pm/day on here. I wrote you with my gmail account. Otherwise - as the topic of my PM fits also in here, would you mind explaining me the CPFP process in this topic? Or maybe just send me another pm with the steps? All you wrote was correct btw.

Thanks a lot & Cheers!!

It's actually quite hard to explain this in detail... This is why i made a wizard a long time ago...
1) surf to http://www.mocacinno.com/page/feechecker
2) enter the transactionid of the stuck transaction
3) near the bottom of the page, you'll see a section called CPFP
4) this section has (in your case) 2 buttons: one creating a CPFP with the unspent output that went to the other party, one creating a CPFP with the unspent output that went to your change address. Obviously, you need to select the button creating a CPFP with the unspent output to your change address (since you don't posses the other party's private keys).
5) double check, tripple check, quadripple check the transaction, i would suggest not to use the decoder on my site alone, but also run the raw transaction trough a thirth party raw transaction decoder like https://blockchain.info/decode-tx
6) if you're happy with the end result, you need to sign the raw transaction... Open the debug console again, and type "signrawtransaction [therawtransaction". The output will be a signed, raw transaction
7) try a different raw transaction decoder, check for the 100th time
if you're happy with the end result, open your debug console and type "sendrawtransaction [rawsignedtransaction]"

That is really nice of you, thanks! I get the steps I have to do but I don't have the neccessary knowledge to fully comprehend what is happening. With checking the transaction you mean the addresses displayed in the raw transaction decoder?

well, you need to double check that the input (vin) is indeed the unconfirmed unspent output to your change address, then you need to double check that the address being funded by the output (vout) is indeed your address, and that the value is indeed the value of the input minus a rather big fee. You can either trust my wizard and assume that the difference between inputs and outputs is suffienctly large as a fee, or you can manually re-calculate the fee... It's up to you

Moca thank you so much for your kind support! In the end I didn't want to screw up anything as the amount being transferred was too valuable, so I used a paid accellerator service. It did help though to actually learn technical stuff concerning BTC - Your support is awesome - There's a tip on the way for your help. Thanks again mate!