Cheers everyone.
Topic: Transactions stuck? (Read 1281 times)
Ah, fair enough, I'll leave them where they are and hopefully they'll sort themselves out. Nothing's important, it's just a small wallet for tinkering with.
Cheers everyone.
Cheers everyone.
You can:
- Wait
- Delete the TX from your wallet using pywallet and wait until it falls in oblivion on the network, which should not take more than a few hours. Unfortunately, the QT client, in that case, will not update your balance back up - or I never found a way to do so, rescan failed. You'll need to import the private key of the sending address on another wallet, such as blockchain.info, for the balance to be right, and spend it from here.
- Wait
- Delete the TX from your wallet using pywallet and wait until it falls in oblivion on the network, which should not take more than a few hours. Unfortunately, the QT client, in that case, will not update your balance back up - or I never found a way to do so, rescan failed. You'll need to import the private key of the sending address on another wallet, such as blockchain.info, for the balance to be right, and spend it from here.
Normal 0.8.3 on Windows.
So, how do I fix this?
So, how do I fix this?
What client are you using? The tx is "low priority" however the included fee (0.01 mBTC) which is smaller than the min mandatory fee on low priority txs (0.1 mBTC). The reference client should have prevented you from creating this transaction. Most miners running default rules will ignore these transaction as denial of service attempts, in fact most nodes will refuse to even relay this transaction for the same reason.
Long story short, I've got some stuck transactions. They've been sat at 0 confirmations for most of the day. One was incoming from my p2pool machine, which looks like it's happened twice. The second was an outgoing, which is equally stuck. Bitcoin looks connected with 9 connections to the bitcoin network.
It looks like one transaction has happened twice, as there's some money in "Unspendable".
http://blockchain.info/fb/1gy44
Any ideas?
It looks like one transaction has happened twice, as there's some money in "Unspendable".
http://blockchain.info/fb/1gy44
Any ideas?
Jump to: