.:::: STUCK BTC TRANSACTION ::::.

[o_e_l_e_o]

waiting long time, infinite time?

Long time, maybe. Infinite time, no.

If you do not re-broadcast your transaction, then there are two main ways it can drop out of the mempool without being confirmed. Firstly, it can be pushed out the bottom of the mempool when the node reaches its maximum mempool size. By default this is 300 MB, but nodes are free to change this. At the moment the mempool is around 50 MB, so this method is unlikely. Secondly, it can be dropped from the mempool when it reaches the expiry time. By default this is 336 hours (14 days), but again nodes are free to change this. Given that your transaction has now been unconfirmed for 9-10 days, then in a few more days it should drop from most nodes and you can try again with a higher fee, which you will need to include from other inputs (or use the same inputs but send less to the recipient).

[1715404569]

1715404569

[1715404569]

1715404569

[HCP]

Looking at the screenshot... you still have 0.00622436 BTC (~6.22436mBTC) remaining in the wallet after the "unconfirmed transaction". You should, theoretically, be able to use this, along with the change from the "unconfirmed transaction" in a "Child Pays For Parent" transaction.

However, based on the info from your previous posts, due to your wallet using Legacy addresses, the total size, across both the unconfirmed and the CPFP transactions, would be at least 4100 bytes... at a rate of 100 sats/byte (which should hopefully get a confirmation within a few hours), you would be paying a total fee of ~0.00410000 BTC in fees!!?!

You could "gamble" and try using 50 sats/byte (currently around 4-5 blocks from the Tip) and mark the CPFP transaction as "RBF enabled"... that way if it is still taking too long, you could bump the fee later.


This case is the perfect illustration of:

1. Why users should seriously consider moving to SegWit (to reduce total transaction sizes and therefore reduce total fees)

and

2. Why users should consolidate UTXOs in their wallets when fees are at low levels. ie. Only using 1 or 2 legacy inputs to a transaction (instead of 26!!?! ), drastically reduces the overall transaction size, which drastically reduces the total fees required.