Post
Topic
Board Bitcoin Technical Support
Merits 2 from 2 users
Re: SPAM TX with 79 recipients and 860 Sat to each blocking my funds
by
o_e_l_e_o
on 13/09/2023, 13:06:04 UTC
⭐ Merited by khaled0111 (1) ,Charles-Tim (1)
I've rewritten your transactions OP to remove the dust input, keep the payment output the same, and very slightly adjusted the fee so you can replace your currently unconfirmed transaction:

Code:
0100000001192aabd987ff508dfda0e10448bfcb1b2cc7281d5b4fa8f77208d13543965c62010000001f144a0ee83923483d4aa9a38b2e5f4ad6650728a72600081b889b0600000000fdffffff0280778e060000000017a914e7a88359fe98b9774a2d6cdbecfb81090ff29c6c8743f50c00000000001976a9144a0ee83923483d4aa9a38b2e5f4ad6650728a72688ac00000000

If you can sign this and broadcast it to a node which accepts full RBF replacements, then it should replace your other transaction and be confirmed fairly quickly. You can do this easily with Electrum if you are able to import your wallet to Electrum using either your seed phrase or a private key for that address. You should do this on an airgapped device for security reasons.

Otherwise, at the effective fee rate of ~7.5 sats/vbyte, you are going to be waiting weeks for a confirmation.

It's nearing the bottom of mempools with default size setting.
The parent transaction with a fee rate of 6 sats/vbyte will already have been dropped by default nodes, meaning OP's should have been dropped as well. There are however an increasing number of nodes using non-default mempool settings, which is why we can still see OP's transaction on block explorers and he can still see it in his wallet.