Hello,
I made a new transaction
Transaction ID: 92232a1d22edec544a99d49c0cd8344f2fd0c925107e4b9dae6ca2a5d0646e51
Transaction total size: 224 bytes
Which falls within the 0.0000014-0.0000015 block from https://bitcoinfees.earn.com/
Lets hope it goes through.
Topic: 2 unconfirmed transactions - not eligible for abandonment (Read 319 times)
Hello,
Thanks for the clear and detailed answer, As I said... I made a mistake then attempted to correct it which caused even more issues haha.
Bitcoin 12 didnt have the option of abadon, upgraded to 15.1 - simply abandoned the transaction it worked.
Thank you all.
Thanks for the clear and detailed answer, As I said... I made a mistake then attempted to correct it which caused even more issues haha.
Bitcoin 12 didnt have the option of abadon, upgraded to 15.1 - simply abandoned the transaction it worked.
Thank you all.
The problem is that your FIRST transaction: https://btc.com/eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e
has paid ZERO fees.
It is highly unlikely that this transaction will EVER confirm as it has not propagated well and most nodes will refuse to relay it, so a miner is unlikely to see it in the first place... let alone include it in a block with 0 fee.
Your SECOND transaction: https://btc.com/3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb#in_0
is attempting to spend the unconfirmed output from the first... Obviously, it can never confirm until the first one does... and as mentioned previously, the first one is unlikely to ever confirm.
You should start Bitcoin Core using the "-walletbroadcast=0" from commandline (or add "walletbroadcast=0" entry in bitcoin.conf). This will prevent your wallet from attempting to rebroadcast these transactions.
Then, right click the transactions in your transaction history and select "abandon transaction"... then shut down Bitcoin Core... and restart it with "-zapwallettxes" (you can remove the -walletbroadcast=0 option at this point)
This should remove the transactions from your transaction history, so your wallet will no longer rebroadcast them. You should then be able to attempt to send out transactions using PROPER fees! refer to:
https://bitcoinfees.earn.com/
https://btc.com/stats/unconfirmed-tx
has paid ZERO fees.
It is highly unlikely that this transaction will EVER confirm as it has not propagated well and most nodes will refuse to relay it, so a miner is unlikely to see it in the first place... let alone include it in a block with 0 fee.Your SECOND transaction: https://btc.com/3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb#in_0
is attempting to spend the unconfirmed output from the first... Obviously, it can never confirm until the first one does... and as mentioned previously, the first one is unlikely to ever confirm.
You should start Bitcoin Core using the "-walletbroadcast=0" from commandline (or add "walletbroadcast=0" entry in bitcoin.conf). This will prevent your wallet from attempting to rebroadcast these transactions.
Then, right click the transactions in your transaction history and select "abandon transaction"... then shut down Bitcoin Core... and restart it with "-zapwallettxes" (you can remove the -walletbroadcast=0 option at this point)
This should remove the transactions from your transaction history, so your wallet will no longer rebroadcast them. You should then be able to attempt to send out transactions using PROPER fees! refer to:
https://bitcoinfees.earn.com/
https://btc.com/stats/unconfirmed-tx
Bitcoin Client Software and Version Number: 12.1
Operating System: Mac OSX
System Hardware Specs: V 10.13.1
Description of Problem: 2 unconfirmed transactions
Any Related Transaction IDs:
Trans ID : 3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb
Trans ID : eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e
Log Files from the Bitcoin Client:
I have sent it to a marchant site.. It would seem they see it in their networks and all, however there is still 0 confirmation on both, and only the second one is pushing on 8 nodes... I dont know what to do(edited)
2017-11-23 18:12:29 ResendWalletTransactions: rebroadcast 2 unconfirmed transactions
2017-11-23 18:13:19 UpdateTip: new
It attempted already 3 times to be taken by a block, all refused. Now the question is what can i do
Blocks 495762-495771 - all refused, still ongoing
Trans ID : 3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb
Trans ID : eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e
I read another thread https://bitcointalksearch.org/topic/2-unconfirmed-transactions-not-eligible-for-abandonment-1961518
However no direct solution was found - only a member @cyyap95 who from my understanding validated them...
If anyone has any idea...
FYI I installed bitcoin core 15.1 So i have both.
Operating System: Mac OSX
System Hardware Specs: V 10.13.1
Description of Problem: 2 unconfirmed transactions
Any Related Transaction IDs:
Trans ID : 3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb
Trans ID : eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e
Log Files from the Bitcoin Client:
I have sent it to a marchant site.. It would seem they see it in their networks and all, however there is still 0 confirmation on both, and only the second one is pushing on 8 nodes... I dont know what to do(edited)
2017-11-23 18:12:29 ResendWalletTransactions: rebroadcast 2 unconfirmed transactions
2017-11-23 18:13:19 UpdateTip: new
It attempted already 3 times to be taken by a block, all refused. Now the question is what can i do
Blocks 495762-495771 - all refused, still ongoing
Trans ID : 3f0725d8af325096c86aa58e7323a8f7157668840323d979b99ee0038a6ab2eb
Trans ID : eec7c8cb54bd68ad8327dcb7ce4358534306ab5a96758051812f4fa73822396e
I read another thread https://bitcointalksearch.org/topic/2-unconfirmed-transactions-not-eligible-for-abandonment-1961518
However no direct solution was found - only a member @cyyap95 who from my understanding validated them...
If anyone has any idea...
FYI I installed bitcoin core 15.1 So i have both.
Jump to: