Bitcoin Forum

Hi,

I tried to do a double spend to release a stuck transaction but think I've done it wrong. The second trx went through ok but the 1st one is still stuck.

They were sent to address

39CFaqwy8TfcAXH9AzAZrTb8DqgkBYGCzf

Here are the Trx ID's

6e6acddf9fdb2762565dca1dc0bd670c3be88fb36ba39f9d29487cf27d26216d

f3431e9b795b1645d1feed966ed06fb947644dca117acfe9f2354e4811a6d6fb

Can anyone help please?

The first one is confirmed (17 confirmations) and second one does not exists.
I think everything is OK.

Hi,

It says it doesn't exist on blockchain but it does exist on bitaps

https://bitaps.com/39CFaqwy8TfcAXH9AzAZrTb8DqgkBYGCzf

I'm really confused

Well, I'm using blocktrail.com and blockchain.info  ... both shows the first confirmed and second non-existing ... seems like issue on the bitaps side (obsolete data)

I sent the transaction through Bitcoin core, do you think it will come back eventually? This is taken from Bitcoin core

Status: 0/unconfirmed, in memory pool
Date: 07/12/2017 22:22
To: 39CFaqwy8TfcAXH9AzAZrTb8DqgkBYGCzf
Debit: -0.08812707 BTC
Transaction fee: -0.00000372 BTC
Net amount: -0.08813079 BTC
Transaction ID: f3431e9b795b1645d1feed966ed06fb947644dca117acfe9f2354e4811a6d6fb
Transaction total size: 372 bytes
Output index: 1

No, I  think your 1st tx already went through which made the second one invalid (thus should be remove from mempool).
To me it looks like bitaps did not updated their mempool (remove the doule spend tx) thus you can still see it.

EDIT: I tried blockexplorer.com as well with the same result  ... thats 3 vs 1 so I'm pretty sure about it.
And it seems your core is outdated as well. I'm not core user so can't help you .... maybe some rescan database or similar option ??

The Bitcoin from the unconfirmed transaction has diappeared from my wallet though, will it come back?

Yes, once your core database gets up to date. But I have no idea how to do that ... wait for some other users reply.

To make it more clear ...The second transaction actually did not happened ( it was automaticaly droped when the first one got confirmed ). But somehow your core database didn't drop it.

Thank-you so much for your help. I'll see if there is a rescan database option or something.

Just to double-check I did the double-spend correctly. I just sent the exact same amount to the same address with a larger fee - is that correct?

Just out of interest, the unconfirmed transaction never seemed to appear in blockchain as far as I could see, only in bitaps. This was even before I did the second transaction.

Just to clarify, the 1st trx did not go through. The second one did. If that makes any difference.

Maybe just restart the core helps.
As of second part I'm not authorized to answer it. Though to me it seems as correct procedure.

Just my 2 cents: bitaps is the closest node to your location, thus received the info about the 2nd transaction .... but at the very same moment the 1st one got confirmed thus other nodes refused it (the 2nd one).

I'm refering 1st and 2nd tx as per your OP (1st - 6e6ac...  2nd - f3431e...)

I see!

I've downloaded the latest core, see if that helps. It seems to be updating the database.

Actually you didn't double spend.

Your first transaction had 2 inputs. While your second transaction had 1 input. The inputs values of both transactions do not match.

However your first transaction will probably never confirm as it was sent with 1 sat/byte.
Most mempools will drop unconfirmed transactions after 72 hours, so you just have to wait.

I had a feeling I didn't do the double spend correctly. I hope the transaction gets dropped soon.