Bitcoin Core - Conflicted Transaction?

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: koinsuka on September 23, 2015, 09:04:20 AM

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.

koinsuka

full member

Activity: 164

Merit: 100

Zap.org - Data Feed Oracle Marketplace

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

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: Dannie on September 21, 2015, 01:18:48 PM

Quote from: shorena on September 17, 2015, 03:14:38 PM

Quote from: Dannie on September 17, 2015, 11:35:47 AM

Quote from: Rmcdermott927 on September 12, 2015, 09:03:42 PM

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 Wink

Dannie

legendary

Activity: 910

Merit: 1000

Quote from: shorena on September 17, 2015, 03:14:38 PM

Quote from: Dannie on September 17, 2015, 11:35:47 AM

Quote from: Rmcdermott927 on September 12, 2015, 09:03:42 PM

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

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

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

Quote from: Dannie on September 17, 2015, 11:35:47 AM

Quote from: Rmcdermott927 on September 12, 2015, 09:03:42 PM

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

legendary

Activity: 910

Merit: 1000

Quote from: Rmcdermott927 on September 12, 2015, 09:03:42 PM

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.

Rmcdermott927

legendary

Activity: 2254

Merit: 1140

Still no clue?

Rmcdermott927

legendary

Activity: 2254

Merit: 1140

Quote from: Rmcdermott927 on September 13, 2015, 06:07:44 AM

Quote from: Undermood on September 13, 2015, 03:00:47 AM

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

legendary

Activity: 2254

Merit: 1140

Quote from: Undermood on September 13, 2015, 03:00:47 AM

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?

Undermood

legendary

Activity: 950

Merit: 1000

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!

odolvlobo

legendary

Activity: 4438

Merit: 3387

A conflicted transaction means that you tried to double spend somehow, according to this thread: https://bitcointalksearch.org/topic/how-to-delete-conflicted-transactions-970008

Rmcdermott927

legendary

Activity: 2254

Merit: 1140

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.

Topic: Bitcoin Core - Conflicted Transaction? (Read 2174 times)