Extremely slow confirmation time - STUCK? * Resolved *

[EBK1000]

I made a transfer as per below and by mistake I must have sent it with a lower than recommended fee and now it seems to take a very long time for the transfer to be confirmed?

Date: 13/10/2015 20:37
To: 15jWJMoKpEUoVADccQvn5hdB9b5YbxDNG1
Debit: -0.45027087 BTC
Transaction fee: -0.00000372 BTC
Net amount: -0.45027459 BTC
Transaction ID: ffc80722c65354cfc0d9b8d71ec237d4ef0895908ebc41128cafc5a2c096fa1d-000



In the blockchain screenshot above it says estimated confirmation time within 6 blocks but there has now been 97 blocks and no confirmations? Is there a way to tell when a transfer will be confirmed and how long might this take? Whats the worst case scenario?

Also, I am sure that I chose the recommended fee but I must have made a mistake or has anyone else experienced this?

[kingofbitcoin]

If its like the screenshot it will go through eventually don't worry.

[shorena]

There are still ~80k TX from the spam[1] it looks like the fee is not high enough to jump the queue.

[1] http://statoshi.info/dashboard/db/transactions

[EBK1000]

There are still ~80k TX from the spam[1] it looks like the fee is not high enough to jump the queue.

[1] http://statoshi.info/dashboard/db/transactions

What are you saying? That the fee is so low that the transaction will forever get stuck?

[shorena]

There are still ~80k TX from the spam[1] it looks like the fee is not high enough to jump the queue.

[1] http://statoshi.info/dashboard/db/transactions

What are you saying? That the fee is so low that the transaction will forever get stuck?

No, not forever, but it might take significantly longer than usual.

If you go to the linked page and scroll down a bit you can see the fee per Kbyte TX paid. Its somewhere between 30k and 50k.  You pay 372 satoshi per 372 byte, or 1k per KByte, thus I assume you are not near the top of the queue.

From the TX ID you listed I also see that you use bitcoin core. If you use a recent version it should come with a fee slider that can predict how long your TX will take to confirm. This is way more accurate than e.g. the rough one from blockchain.info, but it will need some time to gather data. If you start core, sync, issue a TX and close it, the prediction might not be accurate.

[1Referee]

Blockchain.info only gives a rough estimate on when your transaction might get its first confirmation. Better to not look at their useless information. You can only wait and hope it will get included today. You can also set a standard minimum fee to be included in your client. This way you mostly get your transaction confirmed within a few blocks.

[EBK1000]

The issue is that I am sure that I chose the fastest time and selected to pay the standard fee, I always do, I have this feeling that something went wrong somehow?

[shorena]

The issue is that I am sure that I chose the fastest time and selected to pay the standard fee, I always do, I have this feeling that something went wrong somehow?

How long did you have core open before you did that?

[Mickeyb]

The issue is that I am sure that I chose the fastest time and selected to pay the standard fee, I always do, I have this feeling that something went wrong somehow?

Well you haven't paid a standard fee, you have paid a very low fee. Don't worry, your transaction will eventually get confirmed. There are no any stresses in the network for a moment, so it will go through. I just hope that you don't need this confirmed asap!

In the future, send always with 0.0001. I mean this is 2.5 cents. That's nothing. I send sometimes even with 0.0002 if I need absolutely fast confirmation and I can't afford the risk of waiting.

[DannyHamilton]

If it takes too long to confirm, then most of the network may forget about the transaction and you may need to re-broadcast it.

Typically Bitcoin Core will automatically re-broadcast unconfirmed transactions for you if you leave it running, but if you shut down bitcoin core, then it won't re-broadcast until you start it back up and it synchronizes again.  You can rebroadcast it yourself by pushing the raw hex transaction from any of the websites that offer that service.  Here's the raw hex transactions:

Code:

0100000002fa8ea2829622d703334a597320b8bcd3b9ccfaaba39f5a23b6cf5a6de0520911000000006a47304402200559036d1c492ea8102795752078e31df3893dae7034f730792133473045b90c022023edfd29a72c6a8fdc1b25472c7c0b58563de0a66bfcc28ae3cc2620b47e1b4f012102675cb01198065b0537d9a8dcd2be1de5502c0c531a6683fdf61ceebd5e4aea39feffffffd705246a962a69da0aff6fce16c287b7723a4c775ff6c9f36e388fcfcdda9ea8000000006a47304402200490861a3cd66cb1dd1e6436c425d5d8c5dea80f6363801da937d2932691721002205d673eb665c04676aad36521f25ae5b562ed4a5b4992d07f99e9a88f00eefca40121039bc3278387b3e73b857bc3f0219c06b8f78d5206722e147b1d481c3f43945f69feffffff0287652900000000001976a914418fe8f69aea85ef2e13379e0c92654300a0fcd788ac0f0faf02000000001976a91433ea6e6c7930f2346cecc119ed0a105c53f19aae88ac6ec70500

[EBK1000]

If it takes too long to confirm, then most fo the network may forget about the transaction and you may need to re-broadcast it.

Typically Bitcoin Core will automatically re-broadcast unconfirmed transactions for you if you leave it running, but if you shut down bitcoin core, then it won't re-broadcast until you start it back up and it synchronizes again.  You can rebroadcast it yourself by pushing the raw hex transaction from any of the websites that offer that service.  Here's the raw hex transactions:

Code:

0100000002fa8ea2829622d703334a597320b8bcd3b9ccfaaba39f5a23b6cf5a6de0520911000000006a47304402200559036d1c492ea8102795752078e31df3893dae7034f730792133473045b90c022023edfd29a72c6a8fdc1b25472c7c0b58563de0a66bfcc28ae3cc2620b47e1b4f012102675cb01198065b0537d9a8dcd2be1de5502c0c531a6683fdf61ceebd5e4aea39feffffffd705246a962a69da0aff6fce16c287b7723a4c775ff6c9f36e388fcfcdda9ea8000000006a47304402200490861a3cd66cb1dd1e6436c425d5d8c5dea80f6363801da937d2932691721002205d673eb665c04676aad36521f25ae5b562ed4a5b4992d07f99e9a88f00eefca40121039bc3278387b3e73b857bc3f0219c06b8f78d5206722e147b1d481c3f43945f69feffffff0287652900000000001976a914418fe8f69aea85ef2e13379e0c92654300a0fcd788ac0f0faf02000000001976a91433ea6e6c7930f2346cecc119ed0a105c53f19aae88ac6ec70500

I tried to rebroadcast and I got this message "Error validating transaction: transaction already in pool" at https://live.blockcypher.com/

How long does it take before a transaction is failed and I get the BTC back in the wallet?

[EBK1000]

Is there a way to cancel a Bitcoin transaction before it has been confirmed?

https://live.blockcypher.com/btc/tx/ffc80722c65354cfc0d9b8d71ec237d4ef0895908ebc41128cafc5a2c096fa1d/

It suggest that there is a double spend? What can I do in this case?

Reward for a solution!

[achow101]

Is there a way to cancel a Bitcoin transaction before it has been confirmed?

https://live.blockcypher.com/btc/tx/ffc80722c65354cfc0d9b8d71ec237d4ef0895908ebc41128cafc5a2c096fa1d/

It suggest that there is a double spend? What can I do in this case?

Reward for a solution!

Your transaction is double spent because of the transaction malleability attack.

I would recommend using Child Pays For Parent to make this work. You need to create another transaction that spends from this one, hopefully one of those outputs is a change output. Make sure the fee you set is high, high enough for the 2 normal transactions and then a little extra just to be safe. Then push the tx through eligius (http://eligius.st/~wizkid057/newstats/pushtxn.php) so that they mine the transaction since they are the only pool that currently supports CPFP.

[EBK1000]

Is there a way to cancel a Bitcoin transaction before it has been confirmed?

https://live.blockcypher.com/btc/tx/ffc80722c65354cfc0d9b8d71ec237d4ef0895908ebc41128cafc5a2c096fa1d/

It suggest that there is a double spend? What can I do in this case?

Reward for a solution!

Your transaction is double spent because of the transaction malleability attack.

I would recommend using Child Pays For Parent to make this work. You need to create another transaction that spends from this one, hopefully one of those outputs is a change output. Make sure the fee you set is high, high enough for the 2 normal transactions and then a little extra just to be safe. Then push the tx through eligius (http://eligius.st/~wizkid057/newstats/pushtxn.php) so that they mine the transaction since they are the only pool that currently supports CPFP.

It now says this is the wallet:

Status: conflicted, broadcast through 290 nodes
Date: 13/10/2015 20:37
To: 15jWJMoKpEUoVADccQvn5hdB9b5YbxDNG1
Debit: -0.45027087 BTC
Transaction fee: -0.00000372 BTC
Net amount: -0.45027459 BTC
Transaction ID: ffc80722c65354cfc0d9b8d71ec237d4ef0895908ebc41128cafc5a2c096fa1d-000

ED:

It seems one of the transactions did go through after all:

TxID: 2a7f9e0ec622225b1ac93c622dd4ec0bb4cc4587f2fa9b6d5509857141dd2355

But this is not the TxID I created when I sent it from the wallet so what is going on here?

[shorena]

-snip-
It seems one of the transactions did go through after all:

TxID: 2a7f9e0ec622225b1ac93c622dd4ec0bb4cc4587f2fa9b6d5509857141dd2355

But this is not the TxID I created when I sent it from the wallet so what is going on here?

Thats the attack knightdk was talking about. It creates a twin TX with a different TX ID. Both have a chance to get confirmed.

To remove the conflicted TX from the wallet you have to start it with -zapwallettxes

[EBK1000]

-snip-
It seems one of the transactions did go through after all:

TxID: 2a7f9e0ec622225b1ac93c622dd4ec0bb4cc4587f2fa9b6d5509857141dd2355

But this is not the TxID I created when I sent it from the wallet so what is going on here?

Thats the attack knightdk was talking about. It creates a twin TX with a different TX ID. Both have a chance to get confirmed.

To remove the conflicted TX from the wallet you have to start it with -zapwallettxes

But the transactions got through to the recipient BTC address so the attack then must have been unsuccessful or am I missing something? Was I being attacked somehow, my BTC wallet or where does this kind of attack come from?

Is there a reason why I need to remove the conflicted TX from my wallet? As far as I am concerned my payment went through.

[shorena]

-snip-
But the transactions got through to the recipient BTC address so the attack then must have been unsuccessful or am I missing something? Was I being attacked somehow, my BTC wallet or where does this kind of attack come from?

No, they cant change any information about where the coins go, because they dont have the private key(s). Its just an annoying kind of attack, not a critical your coins get stolen kind.

Is there a reason why I need to remove the conflicted TX from my wallet? As far as I am concerned my payment went through.

Not sure what the long term implications are honestly. I just found it annoying so I removed it. If you want, let it be for now and check back here if you need it removed at a later date.