If your transaction has been flagged as RBF, you can replace it with a new one paying higher fee easily.
To be able to do so, you should use a wallet which supports RBF.

It may worth mentioning that there are many nodes that have enabled full RBF and accept the replacement transaction with a higher fee even if the original one has not been flagged as RBF.

Transaction fees are not paid in dollars. We pay the transaction fee in bitcoin and what matters is the fee rate (in sat/vbyte), not the total fee and not its fiat value.


Blockchain.com has a non-custodial wallet in which the user has full control over the keys.

Blockchain.com wallet doesn't have lower fees.

Take note that all the fee you pay when making a transaction from a non-custodial wallet goes to miners and non-custodial wallets doesn't charge you any extra fee at all.
The fee you have to pay depends on number of inputs and outputs, address(es) type, how congested the network is and how fast you want your transaction to confirmed.

Different (non-custodial) wallets may use different methods for fee estimation and many of them even allow you to set the fee rate by yourself.

It's only custodial services like exchanges that charge high fees when you request a withdrawal.  

The next halving will happen once the block number 840,000 is mined. This doesn't have anything to do with how many transactions are included in each block and how many blocks have been mined without containing any (non-coinbase) transactions.
Note that even if a block doesn't have any (non-coinbase) transaction, that's still a block.

Trust wallet is a non-custodial wallet and it doesn't charge you any extra fee. All the fee you pay when making a transaction on trustwallet goes to miners.
Note that whatever wallet you use, you have to pay fee to miners, so that they include your transaction in the blockchain.

The network is so congested. At the time I am writing this post, the required fee rate for getting confirmation is around 310 sat/vbyte.  
If you have used lower fee rate for your transaction and you want to get confirmation now, you should increase the fee rate to 310 sat/vbyte.


Mempool and ETA are two different methods used by electrum to estimate the required fee rate.
With choosing static option, you can select the fee rate to 1, 2, 5, 10 and so on. Electrum also allow you to set the fee rate manually to any amount you want.

Take note that what matters is the fee rate you used for your transaction. It doesn't matter which method you used.
The more fee rate you use, the faster your transaction can be confirmed.


What matters is the fee rate, not the fiat value of the fee.

Are you saying you did CPFP for your first transaction?
With doing CPFP, electrum sends the fund received in the unconfirmed transaction to one of your own addresses, but the address bc1qcr2ntkxyg5aep2qv35wrdpsydzzwa34rwfs6xf which was used as receiving address in second and third transactions doesn't belong to your wallet.


To add to o_e_l_e_o's post:
If you want to make a new transaction including only 1 input, you need to connect to a server which doesn't have your transaction in its mempool. If electrum is displaying status of your transaction as unconfirmed, try connecting to different servers until the status changes to local. Some nodes should have dropped your transaction from their mempool while some other should still have it.

Right click on your local transaction and select "Remove". After that you will need to use coin control to make a transaction with only 1 input.

The error message mentioned by OP doesn't mean he/she doesn't have enough balance for increasing the fee. That error was given by the server when broadcasting the transaction and it means that the fee used for replacement transaction wasn't enough and it didn't meet BIP125 rules.

Do you have control over the receiving address? If so, you can do CPFP.

To do CPFP, you should spend the fund received in the unconfirmed transaction in a new transaction with a high fee.
If the fee paid for the new transaction is high enough for both transactions, miners will include them in the same block.

In the case your wallet doesn't allow you to spend unconfirmed coins, you should import your seed phrase/private key in a wallet which allow you to do so. A good option is electrum.

We can be sure that OP's wallet is synced and he/she isn't talking about the red network circle.
If OP's wallet wasn't sycned, the wallet wouldn't display the transaction history. Also, OP is getting an error from a server and that means that his/her wallet is definitely connected to a server.

The unconfirmed parent means that you are spending the fund that has been received in an unconfirmed transaction.
The solution is to increase the fee, so that miners includes both parent and child in the same block.


If the fee used for the replacement transaction is lower than the fee paid for the original transaction, electrum doesn't allow you to click on "OK" button at all.
You get the error mentioned by OP, when the fee paid for the replacement transaction is higher than original transaction, but that's not enough.

The fee rate displayed on mempool.space is just an estimation of the required fee rate and that's not necessarily the fee rate used by your wallet when making a transaction. Your wallet may use a different method for fee estimation and use a different fee rate.
You should use mempool.space or similar tools when you want to set the fee manually.

The second and third transactions increased the effective fee rate of the first transaction and they can be considered as CPFP transactions, but that's not why OP made those transactions.
If OP had used CPFP option on electrum, those transactions would include only one receiving address.

With doing so, the two other transactions would be invalidated.
If OP wants  all three transactions to be confirmed fast, he/she must bump the fee rate of the third transaction.


The network is so congested now and the required fee rate for getting fast confirmation is now around 170 sat/vbyte.
The total (virtual) size of the transactions is 1192 vbyte. This means the fee rate required for these three transactions to be confirmed fast is now around 200,000 satoshi.

The total fee that has been paid for the first and second transactions is 36,244 satoshi and this means that around 160,000 satoshi needs to be paid for the third transaction.
If the fee rate of the third transaction is bumped to around 850 sat/vbyte, all three transactions will be probably confirmed fast.

The network is so congested now and the fee rate used for the first transaction is very low.
The second transaction is using the fund received in the first transaction as change and the third transaction is spending the fund received in the second transaction.

As long as the parent is unconfirmed, the child can't be confirmed.

The problem is probably with the base unit. The base unit has been set to mBTC and OP is entering the amount in BTC.


This is not accurate. You can't make a transaction creating an output which is smaller than the dust limit.
As I said in my previous post, the dust limit is 546 satoshi for legacy addresses and 294 satoshi for native segwit addresses.

Rebroadcasting a different from acceleration. There are many other websites that allow you to (re)broadcast your transaction freely.

With rebroadcasting your transaction, you only broadcast it again and its only effect is that if a node has dropped your transaction from its mempool, it may receive and put your transaction in its mempool again.

Note that the fee you pay when making a transaction from trustwallet or any other non-cusotodial wallet goes to miners and you don't pay any fee to trustwallet.
If you make a withdrawal from binance or any other exchange, you have to pay higher fees.


If a transaction stays unconfirmed for 2 weeks, many nodes will drop it from their mempool. But some will still have it in their mempool and it's possible that the transaction is confirmed if the required fee rate decreases.
Also, you are not charged for an unconfirmed transaction.


The minimum fee rate you should set for your transaction, so that you can use ViaBTC free accelerator is 10 sat/byte, not 10 sat/vbyte.


It's true that nodes may receive transactions at different times, but the time that an unconfirmed transaction is kept in the mempool varies from node to node, because nodes can have different setting.
It's possible that two nodes receive a transaction at the same time, one of them keeps it for 2 weeks and the other one keeps it for 1 month.

Nitrobetting userid: 234625
Prediction: $38,670

Did you create a request in electrum receive tab?
If so, take note that you don't have to make any request in electrum to receive bitcoin. You can use any of addresses listed in "addresses" tab to receive bitcoin.

I guess the problem is that the base unit has been set to mBTC and with entering 0.00052172, you make a request to receive 0.00052 mBTC which is equal to 0.00000052 BTC.

Note that any bitcoin address can receive any amount bigger the dust limit.
The dust limit for legacy addresses (those that start with 1) is 546 satoshi and for native segwit addresses (those that start with bc1q) is 294 satoshi.


Again, you don't need to make any request to receive bitcoin.