Quote from: mocacinno on Today at 10:56:30 AM

Number 2 and 3 on your list are ok... Number 1 however can potentially do more harm than good...

And in this case, where the fee rate paid is still firmly within the default mempool limits and not low enough to be purged and the transaction is visible on all block explorers, rebroadcasting achieves nothing. ViaBTC's free accelerate also wouldn't work in this case since the fee paid is below the 10 sats/byte cut off they require.

Quote from: ranochigo on Today at 11:41:32 AM

You can calculate the fees that you need by a simple calculation; calculate the total fees needed for your desired fee rate and calculate the amount of fees your second transaction needs and thus its fee rate.

For illustration: If you send all the bitcoin at the address 16qAvw1qDmJbAR9yeS54yrVe2r38d1T86K to another address within your wallet, and you want to boost the fee rate to 100 sats/vbyte (which is currently what you need for a relatively fast transaction), the total fee you would have to pay for your two transactions together would be 416 bytes * 100 sats = 41,600 sats. Given that you have already paid 1,784 sats, your second transaction would need to pay 39,816 sats in fee. With a presumed size of 192 bytes for a 1-input-1-output legacy transaction, the fee rate for this transaction would need to be ~208 sats/vbyte.