Transaction c264c02f8bd6985595b86394bb64f56ca4f7da21a0ee04bd5c691c97a9bf4ab9 is no longer visible at blockchain.info.
I assume the other transaction eventually confirmed?
Topic: A bit of advice please. I just double-spent. (Read 1053 times)
Hi all,
Yesterday at 1:49pm GMT, I sent 1BTC to localbitcoins. Sadly, I accidentally sent without a transaction fee. As such, it kept getting pushed further and further back in the queue.
Anyway, I read about pywallet, so I followed the guide to clear the transaction from my wallet, and then performed a rescan. Of course, I got the BTC back in my wallet and sent again with the tx fee.
This time, however, blockchain says :
Warning! this transaction is a double spend of XXXXXXXX. You should be extremely careful when trusting any transactions to/from this sender.
Estimated Confirmation Time Possibly Never (queue position 86)
(and the other one is queue position 4860)
Does anyone know how long this situation will take to resolve itself? It's a weird one.
Thanks
Yesterday at 1:49pm GMT, I sent 1BTC to localbitcoins. Sadly, I accidentally sent without a transaction fee. As such, it kept getting pushed further and further back in the queue.
Anyway, I read about pywallet, so I followed the guide to clear the transaction from my wallet, and then performed a rescan. Of course, I got the BTC back in my wallet and sent again with the tx fee.
This time, however, blockchain says :
Warning! this transaction is a double spend of XXXXXXXX. You should be extremely careful when trusting any transactions to/from this sender.
Estimated Confirmation Time Possibly Never (queue position 86)
(and the other one is queue position 4860)
Does anyone know how long this situation will take to resolve itself? It's a weird one.
Thanks
The blockchain.info client captures transaction info even when other Bitcoin clients might ignore it. If you create a junk transaction that nobody will relay, they'll still show it if it gets to them and put a 'double spend' alert even on the one that is valid.
However, your issue is that your 1 BTC transaction qualified to be free if you sent it with Bitcoin-Qt and you were not prompted for a fee (1 BTC can be free after less than a day sitting in your wallet). As such, the first is a legitimate transaction, and other Bitcoin clients and miners won't store another new transaction with a double-spend of its funds. You'll have to wait for the first to go through.
The optional fee in Bitcoin-Qt should be set to 0.0001 per/KB instead of 0, so all transactions have the minimum fee, if you don't want miners pushing back free ones for more profitable transactions.
Why is the second transaction still not confirming?
c264c02f8bd6985595b86394bb64f56ca4f7da21a0ee04bd5c691c97a9bf4ab9
My best guess is that I need to wait until the first one is knocked off, then the other one should not show as a double. Am I right in thinking that?
My best guess is that I need to wait until the first one is knocked off, then the other one should not show as a double. Am I right in thinking that?
What are the transaction ID's?
Never mind. I just read that I need to delete again and wait a few days.
EDIT : Oh wait, I can't. I deleted the transactions again and performed a re-scan. It seems the double-send (2nd one) won't delete.
I better just wait it out and hope for the best.
EDIT AGAIN : I am very very confused now with everything I have read. Could someone please help me to understand what happens now?
EDIT : Oh wait, I can't. I deleted the transactions again and performed a re-scan. It seems the double-send (2nd one) won't delete.
I better just wait it out and hope for the best.
EDIT AGAIN : I am very very confused now with everything I have read. Could someone please help me to understand what happens now?
Hi all,
Yesterday at 1:49pm GMT, I sent 1BTC to localbitcoins. Sadly, I accidentally sent without a transaction fee. As such, it kept getting pushed further and further back in the queue.
Anyway, I read about pywallet, so I followed the guide to clear the transaction from my wallet, and then performed a rescan. Of course, I got the BTC back in my wallet and sent again with the tx fee.
This time, however, blockchain says :
Warning! this transaction is a double spend of XXXXXXXX. You should be extremely careful when trusting any transactions to/from this sender.
Estimated Confirmation Time Possibly Never (queue position 86)
(and the other one is queue position 4860)
Does anyone know how long this situation will take to resolve itself? It's a weird one.
Thanks
Yesterday at 1:49pm GMT, I sent 1BTC to localbitcoins. Sadly, I accidentally sent without a transaction fee. As such, it kept getting pushed further and further back in the queue.
Anyway, I read about pywallet, so I followed the guide to clear the transaction from my wallet, and then performed a rescan. Of course, I got the BTC back in my wallet and sent again with the tx fee.
This time, however, blockchain says :
Warning! this transaction is a double spend of XXXXXXXX. You should be extremely careful when trusting any transactions to/from this sender.
Estimated Confirmation Time Possibly Never (queue position 86)
(and the other one is queue position 4860)
Does anyone know how long this situation will take to resolve itself? It's a weird one.
Thanks
Jump to: