Topic: Un-sticking a transaction stuck in the mempool (Read 168 times)
bump
Hi,
I've got a problem with a transaction which has been stuck in the mempool for around 3 days now. I used electrum to send the transaction and I made the mistake of not setting the fees high enough. On top of that, I didn't enable Replace-By-Fee, and the transaction has only 1 recipient which is an address I don't control, and no change outputs.
In short I did everything possible to make this transaction irreversible.
I just want to know how I can get this transaction to confirm or for the network to forget about it. I wouldn't be worried except the destination address is one I don't control. I'm running a bitcoin core node and have noticed the abandontransaction command. Would this be any help?
Would it be worth a try to import the private key into my node then try to re-broadcast a new transaction which spends the same outputs, in the hope that nodes that haven't heard about the original transaction will replace it with the new one? I know that as a last resort I can pay a miner directly to include the transaction in a block, but I'd rather not pay more than I have to.
I'd rather not share the transaction ID for privacy reasons.
Appreciate any help
I've got a problem with a transaction which has been stuck in the mempool for around 3 days now. I used electrum to send the transaction and I made the mistake of not setting the fees high enough. On top of that, I didn't enable Replace-By-Fee, and the transaction has only 1 recipient which is an address I don't control, and no change outputs.
In short I did everything possible to make this transaction irreversible.
I just want to know how I can get this transaction to confirm or for the network to forget about it. I wouldn't be worried except the destination address is one I don't control. I'm running a bitcoin core node and have noticed the abandontransaction command. Would this be any help?
Would it be worth a try to import the private key into my node then try to re-broadcast a new transaction which spends the same outputs, in the hope that nodes that haven't heard about the original transaction will replace it with the new one? I know that as a last resort I can pay a miner directly to include the transaction in a block, but I'd rather not pay more than I have to.
I'd rather not share the transaction ID for privacy reasons.
Appreciate any help
Jump to: