Abandon Unconfirmed trascaction after double-spend

[Chaotic_4]

I placed two transactions but the remaining balance was not enough for both. At that time I was experimenting with the Coin control. Eventually, one got confirmed but the other remains unconfirmed. Is there any way to remove it from the mempool? The abandon option is not available and it is unconfirmed. Will the nodes of the network remove it at some point? For both of these transactions, the option replace by fee was enabled.

[DaveF]

You can run zapwallettxes google it for proper use based on your OS Windows / linux and it should take care of it.
This is assuming you are running Bitcoin Core.
If you are running another client you will have to do something else.

-Dave

[Chaotic_4]

I use prune mode and the command did not work. Should I use reindex?

[nc50lc]

You'll have to re-download and verify all blocks if you use -reindex because it's a pruned node.
and 'abandon transaction' will only be available if the transaction isn't in your mempool.

Since it's marked as RBF, as a workaround you can manually create a transaction that spends the same input(s) which sends the funds back to your own wallet.
Here's how to create using the console/bitcoin-cli: createrawtransaction | signrawtransactionwithwallet | sendrawtransaction
But if you're fine with the current outputs, just let it be, it'll be confirmed later or dropped after 2weeks approx.

But what's the deal with the thread's title.
Did you double-spent one of the transactions? Because if it was double-spent, it should be out of your mempool by now.

[Chaotic_4]

The two transactions had one common address as input. The remaining balance was not enough for both of the transactions. I don't mind to download the whole blockchain, will the reindex solve the problem?

[nc50lc]

The two transactions had one common address as input.

It's not the address, the one that should be re-spent is the same UTXO that was spent by the to-be-replaced transaction.
You should first check both transactions in the console (Window->Console) using getrawtransaction, eg:

Code:

getrawtransaction "TXID" true

Look for the inputs ("vin"), if at least one of them has exactly the same "txid" and "vout" (under the txid) as the other one's (I think they aren't).

-reindex may not be useful in this case.BTW, -zapwallettxes shouldn't be used in the console, you should launch bitcoin core with it.

[HCP]

The two transactions had one common address as input.

But did they have a common UTXO (from that address)? If they did, then most nodes will have invalidated the 2nd transaction as soon as the first one was confirmed as the "common" UTXO no longer exists to be used in the 2nd transaction.

If you can still see the 2nd transaction on block explorers (and it isn't marked as invalid), then there is a very good chance it wasn't spending the same UTXO(s) as the first transaction as is actually still a "valid" transaction and will eventually get confirmed.

Do as nc50lc suggested and check the UTXOs for both transactions very careful, I concur with them that it would appear that there wasn't a common UTXO, otherwise all the nodes would have invalidated your 2nd transaction.