Topic: Get rid of unconfirmed transaction - already 30 hours (Read 2104 times)
More likely that can't be used anymore as the transaction has already been pruned from blokchain.info's database,also I'm unable to see it in the blockr.Io's mem pool.Try rebroadcasting it again with substantial amount of fees this time.
- snip -
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
It should be -zapwallettxes and you have mistyped it as -zapwallettex, and that's why your unconfirmed transaction is still there in your wallet. For your reference: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
I feel so stupid. Thank you very much! It's working as expected now
Edit: How long will it take others to forget about the previous transactions? My current (new) transaction is declined by the network as double spent.
give it another 18-40 hours.
- snip -
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
It should be -zapwallettxes and you have mistyped it as -zapwallettex, and that's why your unconfirmed transaction is still there in your wallet. For your reference: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
I feel so stupid. Thank you very much! It's working as expected now
Edit: How long will it take others to forget about the previous transactions? My current (new) transaction is declined by the network as double spent.
- snip -
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
- snip -
Transactions are still there and getting broadcasted. I hope you can help me!
It should be -zapwallettxes and you have mistyped it as -zapwallettex, and that's why your unconfirmed transaction is still there in your wallet. For your reference: https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments
Hi all.
My last transaction was in the year 2014. I didn't know that there is such a high load currently so I haven't added nearly any transaction fee. Next time I'll know better.
Anyways. That transaction is unconfirmed for 30 hours now and I really need the BTC for an exchange. That's why I created another transaction which is also unconfirmed and moreover seems to depend on the first transaction (blockchain.info warns: this transaction spends an input which is unconfirmed).
First transaction:
https://blockchain.info/tx/18998e04e973a3d3271bf14a9b0d359e6c43b26c4380f059ba178a46e50d2d38
Second transaction:
https://blockchain.info/tx/0fbc4576ab1e6873070d603aa64da9787e1c961894f93b653be8ddac55088d29
I have two questions now:
1. Can I create a transaction with high fee that is NOT depending on the other two and will get processed soon? From the same wallet of course.
2. How can I delete the unconfirmed transactions? The client should just unlock the BTC and stop broadcasting that transactions. It's okay if they'd get confirmed afterwards (I think that this won't happen anyways).
What I tried so far:
1. Waiting
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
3. Executing abandontransaction which leads to the error "Transaction not eligible for abandonment (code -5)"
Transactions are still there and getting broadcasted. I hope you can help me!
My last transaction was in the year 2014. I didn't know that there is such a high load currently so I haven't added nearly any transaction fee. Next time I'll know better.
Anyways. That transaction is unconfirmed for 30 hours now and I really need the BTC for an exchange. That's why I created another transaction which is also unconfirmed and moreover seems to depend on the first transaction (blockchain.info warns: this transaction spends an input which is unconfirmed).
First transaction:
https://blockchain.info/tx/18998e04e973a3d3271bf14a9b0d359e6c43b26c4380f059ba178a46e50d2d38
Second transaction:
https://blockchain.info/tx/0fbc4576ab1e6873070d603aa64da9787e1c961894f93b653be8ddac55088d29
I have two questions now:
1. Can I create a transaction with high fee that is NOT depending on the other two and will get processed soon? From the same wallet of course.
2. How can I delete the unconfirmed transactions? The client should just unlock the BTC and stop broadcasting that transactions. It's okay if they'd get confirmed afterwards (I think that this won't happen anyways).
What I tried so far:
1. Waiting
2. Starting Bitcoin-Qt with -zapwallettex option like this: exec /Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -zapwallettex
3. Executing abandontransaction which leads to the error "Transaction not eligible for abandonment (code -5)"
Transactions are still there and getting broadcasted. I hope you can help me!
Jump to: