Bitcoin Core - Conflicted Transaction?

[Rmcdermott927]

I sent a tx a few hours ago with the txid of: 4a779f8e44c890dc8f1ffba058c709b01b1aa926247c234943671992a1a50569

It is currently in a *conflicted* state when looking at my transaction history and I can not see the tx on blockchain.info.  Why and how did this happen and is there anything I can do to either fix it or get the funds added back to my wallet?

I did a -rescan and the transaction is still there.

[odolvlobo]

A conflicted transaction means that you tried to double spend somehow, according to this thread: https://bitcointalk.org/index.php?topic=970008.0

[Undermood]

Because your unconfirmed transactions cannot be double spent and after  it dispears from the mempool you would wouldn't find it in block explorer! It will take some hours!

[Rmcdermott927]

Because your unconfirmed transactions cannot be double spent and after  it dispears from the mempool you would wouldn't find it in block explorer! It will take some hours!

So, the offending transaction was never removed from my wallet?

[Rmcdermott927]

Because your unconfirmed transactions cannot be double spent and after  it dispears from the mempool you would wouldn't find it in block explorer! It will take some hours!

So, the offending transaction was never removed from my wallet?

Any ideas?

[Rmcdermott927]

Still no clue?

[Dannie]

I did a -rescan and the transaction is still there.

Instead of doing a -rescan, you should be running your bitcoin core with -zapwallettxes. Take a look at https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments for reference.

[shorena]

I had a similar issue with bitcoin core a while back. Checking all inputs (I use coin control) with several blockchain explorers confirmed that my coins did not move. I fixed it by writing a TX by hand and broadcasting it via one of these interfaces (I dont remember which).

Code:

https://insight.bitpay.com/tx/send
https://coinb.in/#broadcast
https://btc.blockr.io/tx/push

I did a -rescan and the transaction is still there.

Instead of doing a -rescan, you should be running your bitcoin core with -zapwallettxes. Take a look at https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments for reference.

Make sure its -zapwallettxes=1 to keep the labels.

[Dannie]

I did a -rescan and the transaction is still there.

Instead of doing a -rescan, you should be running your bitcoin core with -zapwallettxes. Take a look at https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments for reference.

Make sure its -zapwallettxes=1 to keep the labels.

Indeed, -zapwallettxes is treated exactly the same way as -zapwallettxes=1 by default. Check https://github.com/bitcoin/bitcoin/commit/77cbd46 for your reference.

[shorena]

I did a -rescan and the transaction is still there.

Instead of doing a -rescan, you should be running your bitcoin core with -zapwallettxes. Take a look at https://en.bitcoin.it/wiki/Running_Bitcoin#Command-line_arguments for reference.

Make sure its -zapwallettxes=1 to keep the labels.

Indeed, -zapwallettxes is treated exactly the same way as -zapwallettxes=1 by default. Check https://github.com/bitcoin/bitcoin/commit/77cbd46 for your reference.

Thanks, the wiki needs a note that its 1 by default. Nobody is gonna check the code every time

[koinsuka]

maybe any error at blockchain system, so far as my experience
transaction was done, but you send again with click button 'send' ..

[shorena]

maybe any error at blockchain system, so far as my experience
transaction was done, but you send again with click button 'send' ..

Not sure what you mean with "blockchain system", but bitcoin core said its conflicted, I think the TX never left the machine in the first place.