Electrum Transaction Issue: Unconfirmed Parent; Insufficient fee problem

[Arthem]

Please tell me what needs to be done to make the transaction go through since this did not happen before

The error message is clear. The fee you set for the replacement transaction was not enough and the server rejected that.

Does your transaction have any child?
Can you share the transaction ID?

By the way, you used the wrong tag for your link, and that made it not work.

Thanks for correcting the link!
I have two unconfirmed parents and one unconfirmed|

591e7f0cb19bdcea02d8b0f41b31d863060739943c2dcdfd1223cc2e1c31cf05

[hosseinimr93]

591e7f0cb19bdcea02d8b0f41b31d863060739943c2dcdfd1223cc2e1c31cf05

The transaction has two unconfirmed children. So, for replacing that transaction with a new one, nodes have to remove three transactions from their mempool.
The fee you pay for the replacement transaction must be higher than the total fee paid for those three transactions added by minimum fee required for relaying the replacement transaction.

The total fee paid for those three transactions is 101,611 sat.
The minimum relay fee rate for nodes with default setting is now 1 sat/vbyte and the minimum required fee for relaying the replacement transaction is 788.25 sat.

Therefore, the fee you have to pay for the replacement transaction must be at least 102,399.25 which gives the fee rate of 130 sat/vbyte.

So, if you want to replace the parent transaction with a new one, you should increase the fee rate to at least 130 vbyte.
Take note that you may need to increase the fee rate a bit more, since nodes may have different settings.

Since paying such fee may be expensive for you, you may want to consider waiting for the original transaction to be confirmed.

[nc50lc]

-snip-

I have two unconfirmed parents and one unconfirmed|

If you do not want the two children (labeled with 'Unconfirmed Parent') to be essentially cancelled
once the majority of the nodes accepted the parent's replacement to their mempool or fully invalid once it's confirmed;
You may consider bumping the last child transaction (28322698f7df147c78fe6a326611dc31e85c81ac295a6ec7f487478c8c0905d0) instead.
That's basically a "Child-Pays-for-Parent" CPFP for its two parent transactions.

Its two parents' fees and virtual sizes will be considered when computing the three transactions' overall total fee rate.
e.g.: If you set 120,000 sat as the last child transaction's "new fee" (tick 'Edit fees manually' in the settings icon):
        Total fee rate = (11,835 sat + 12,600 sat + 120,000 sat) / (‎789 vB + 504 vB + 3507 vB)
        30 sat/vB = 144,435 sat / 4,800 vB (given that it wont add another input)

[Arthem]

Thank you all very much! They helped me give birth! All transactions were successful