Author

Topic: And another "Unconfirmed Transaction - 0..." (Read 4544 times)

legendary
Activity: 4214
Merit: 1313
August 20, 2016, 07:19:50 AM
#12
hi, i have same problem, tried to to abandon transaction following instructions here and the output was - transaction is not eligible for abandonment...

is there any chance to add more fees to existing transaction? or any other ways to make it work?


thank you!

What is the transaction ID?
newbie
Activity: 1
Merit: 0
hi, i have same problem, tried to to abandon transaction following instructions here and the output was - transaction is not eligible for abandonment...

is there any chance to add more fees to existing transaction? or any other ways to make it work?


thank you!
staff
Activity: 3458
Merit: 6793
Just writing some code
You do not need to use -zapwallettxes. Instead, you can go to Help > Debug Window and click on the Console tab. Then in the box at the bottom type
Code:
abandontransaction

Wow.  I wasn't aware of that command.  Apparently I haven't done a good job of keeping up with the new features added to the wallet in the past few versions.  I'll have to go read about that now.  Thanks!

Even better is that the next version (0.13, planned to be released in August), will allow you to abandon the transaction right in the GUI on the transactions list.
sr. member
Activity: 260
Merit: 250
Thank you all
legendary
Activity: 3472
Merit: 4801
Since you are using Bitcoin Core, click the "Choose.." button next to the transaction fee. Then move the slider from "normal" to "fast". That will make sure that you use a sufficient fee.

Yep.  That "normal" label really should say "VERY SLOW". That would help avoid a lot of confusion people seem to have about their fees.

You do not need to use -zapwallettxes. Instead, you can go to Help > Debug Window and click on the Console tab. Then in the box at the bottom type
Code:
abandontransaction

Wow.  I wasn't aware of that command.  Apparently I haven't done a good job of keeping up with the new features added to the wallet in the past few versions.  I'll have to go read about that now.  Thanks!
legendary
Activity: 2786
Merit: 1031
Thank you for the answer... didn't understand the fee part correctly Lips sealed
I just sent fee that was suggested by the wallet.
Can I reverse this transaction with -zapwallet and resend it?

As you can see here https://blockchain.info/tx/9de7bc11dbebb450d466063b3173dac5fbe5689704547f6613a57fc5f648a859 your transaction is 225 (bytes), you paid 4484 satoshi fee, if you do the math you come up with 19.93 satoshi/byte, which is low for current network load.

If you were going to make a transaction right now and wanted it included in next few blocks you have to pay at least 60 satoshi/byte.
staff
Activity: 3458
Merit: 6793
Just writing some code
Thank you for the answer... didn't understand the fee part correctly Lips sealed
I just sent fee that was suggested by the wallet.
Can I reverse this transaction with -zapwallet and resend it?
Since you are using Bitcoin Core, click the "Choose.." button next to the transaction fee. Then move the slider from "normal" to "fast". That will make sure that you use a sufficient fee.

You do not need to use -zapwallettxes. Instead, you can go to Help > Debug Window and click on the Console tab. Then in the box at the bottom type
Code:
abandontransaction
where is the transaction id of your transaction. In this case, the is 9de7bc11dbebb450d466063b3173dac5fbe5689704547f6613a57fc5f648a859. This then allows you to resend the transaction but with a higher fee. Keep in mind that this does not make the rest of the network forget your transaction and the replacement transaction will appear as a double spend to everyone else.
legendary
Activity: 3472
Merit: 4801
Thank you for the answer... didn't understand the fee part correctly Lips sealed
I just sent fee that was suggested by the wallet.
Can I reverse this transaction with -zapwallet and resend it?

Yes.

If you are using Bitcoin Core, then you can use -zapwallet to remove the transaction from your wallet.  Your wallet will then let you create a new transaction with a different fee.

However, if the wallet doesn't use the EXACT SAME input, then it might be possible for BOTH transactions to end up confirming (meaning you would have sent twice as much as you intended to). If your wallet only has the one unspent output (or if the other unspent outputs are small enough) this won't be a problem at all. Also, you can completely avoid this potential problem if you use the "coin control" features of the Bitcoin Core wallet and choose the same input.

Additionally, if most of the nodes and miners have already received your first transaction, then they will refuse to accept your new transaction until they drop the old transaction from their memory pool. Therefore, you could end up waiting quite a while for the first transaction to be dropped by everyone before your second transaction then confirms quickly.  Fortunately, your wallet will continue to re-broadcast the transaction occasionally as long as you leave it running, so once peers start dropping the old transaction, they will hear about the new one.

sr. member
Activity: 260
Merit: 250
Thank you for the answer... didn't understand the fee part correctly Lips sealed
I just sent fee that was suggested by the wallet.
Can I reverse this transaction with -zapwallet and resend it?
legendary
Activity: 2786
Merit: 1031
Network has been like shit for quite some time, if you want your transaction confirmed you really need to stay up to date with what's happening right now.

You paid 19,93 satoshi per byte.

As you can see here https://btc.com/stats/unconfirmed-tx there are a few MB of transactions with bigger fee, if people continue to submit transactions your transaction will eventually get dropped, if transaction rate decreases you might get confirmed.
legendary
Activity: 3472
Merit: 4801
I sent with sufficient transaction fee so I can't understand why it still unconfirmed for hours (6 hours).

Unfortunately, you didn't.

The fee you paid is about 20 satoshis (0.00000020 BTC) per byte.

A sufficient transaction fee for the current network load would be about about 70 satoshis (0.00000070 BTC) per byte, which for your 225 byte transaction would be about 15750 satoshis (0.00015750 BTC) instead of the 4484 satoshis (0.00004484 BTC) that you paid.

Under the current network load, I would expect a fee of 20 satoshis to take at least 6 hours to confirm.  If the load increases before the transaction confirms, it could take much more than 6 hours.
sr. member
Activity: 260
Merit: 250
Hi guys,

Can you help me please and explain what's the problem?

Status: 0/unconfirmed, broadcast through 5 nodes
Date: 6/17/2016 12:04
To: 183KHdrWnXcaga6RSo5eLv92xEwYseCxPu
Debit: -2.00000000 BTC
Transaction fee: -0.00004484 BTC
Net amount: -2.00004484 BTC
Transaction ID: 9de7bc11dbebb450d466063b3173dac5fbe5689704547f6613a57fc5f648a859-000

I sent with sufficient transaction fee so I can't understand why it still unconfirmed for hours (6 hours).

Thanks,
Yossi


Jump to: