Due to recent events with mixer being confiscated by authorities, or mixer doing an exit scam, or with a seemingly legitimate pro-privacy company going in the opposite direction, I think a clarification of where we are at the moment in protecting the users' privacy is necessary.

There are three ways to secure privacy of your bitcoins, each of which comes with its own advantages and disadvantages. Pick according to what fits you best.

It absolutely does. Any sane user of a privacy service does not want the fee they pay being handed to blockchain analysis to spy on their inputs and potentially censor those inputs based on their findings. This is antithetical to the entire concept of privacy.

Submarine swaps don't provide any additional privacy than what's already available in the Lightning Network and Bitcoin blockchain. So you can increase the privacy of your Lightning network by routing through multiple channels such as onion routing.

I do not know much about submarine swap, but lightning network will help in having privacy as you open and close a channel. I do not know about Muun wallet, but you can use Electrum to open and close a channel.

Edit:
@xett036
Use Electrum which is not a centralized means of using lightning payment.

Know that if you use a lightning network to open a channel and later close the channel, the coin has been mixed already.

After selecting, click Send tab.
Use ctrl to select more than 1.

To be more precise:
You can specify which UTXO (coin) you want to be used for your transaction.
Note that any address can contain numerous UTXOs (coins)

When you use "pay to many", you pay bitcoin to all recipients in a single transaction and there is no other transaction at all.

Click on "View" at top of the window and select "Show Coins".

I always use Johoe's Bitcoin Mempool Statistics.
To know the current required fee, hover your mouse cursor over right side of the chart.

Look at the screenshot I just took.




The total virtual size of transactions paying at least 1 sat/vbyte is 100 vMB.
The total virtual size of transactions paying at least 2 sat/vbyte is 52 vMB.
The total virtual size of transactions paying at least 3 sat/vbyte is 49 vMB.
...........
...........
...........
The total virtual size of transactions paying at least 17 sat/vbyte is 0.91 vMB.

Note that miners prioritize transactions based on the their fee rate and every block has a capacity of 1 vMB.
So, if I set the transaction fee to more than 17 sat/vbyte, my transaction will likely be confirmed in the next block.
Note that it's possible that new transactions with higher fee rates are added to the mempool and my transaction isn't confirmed in the next block. So, I can pay a bit more (18-20 sat/vbyte) to increase the chance of getting confirmation in the next block.

There are other websites like mempool.space that can be used to estimate the required transaction fee rate.

For the next time: if possible, using "Pay to many" in Electrum gives you lower total fees. You'll have one transaction with multiple outputs and only one change address.

That's how a blockchain works: each transaction uses the output from the previous transaction.

If you have multiple inputs in your own wallet you can use Coin control to avoid this, but you don't need to. It's normal.

If you are in hurry, bump the fee of transaction 2.
If you are not in hurry, just wait.

As calculated, the total virtual size of your transactions is 427 vbyte.
Given that for a fast confirmation, transaction fee of around 14 sat/vbyte is required, you need to pay 5978 satoshi in total.
You have paid 3024 satoshi for transactions 1 and 3 and need to pay 2954 satoshi for transaction 2.
If you are in hurry, bump the fee rate of transaction 2 to 21 sat/vbyte.

You can pay a bit more (around 25 sat/vbyte) to make sure your transaction will be confirmed soon. The fee rate required for a fast confirmation changes over time.


With doing so, you invalidate transactions 1 and 2.
If you want all three transactions to included in the blockchain and you are in hurry, bump the fee of transaction 2.

Note that in my previous post, I had assumed that the order is transaction 1 ---> transaction  2 ---> transaction 3 and that was why I said you should bump fee of transaction 3.
Since the order is transaction 3 ---> transaction 1 ---> transaction 2, you should bump fee of transaction 2.

Again, no need to do anything, if you are not in hurry.

As mentioned by ranochigo, you have made the transaction 1 before transaction 2.
If you want these transaction to be confirmed fast, you should bump the fee of transaction 2

Note that with bumping the fee of transaction 3, you invalidate transactions 1 and 2 and with bumping the fee of transaction 1, you invalidate transaction 2.

Transaction 3 -> Transaction 1 -> Transaction 2.

For transaction 1 to have a confirmation, transaction 3 has to confirm first. Afterwhich, for transaction 2 to confirm, transaction 1 has to have a confirmation first.

What kind of transaction are these for; for a payment, a transfer to someone, a transfer to yourself? You can choose to create yet another transaction(which is mentioned above) or to have a replace-by-fee on transaction 3 which will invalidate transaction 1 and 2. Afterwhich, you can choose to create a new transaction that is similar to transaction 3 and continue with transaction 1 and 2.

Replace-by-fee is cheaper than CPFP.

When electrum says that a transaction has unconfirmed parent, it means that the fund which is being tried to send in that transaction has been received in a transaction which is still unconfirmed.

Assume that you have sent bitcoin from address A to address B and then the same coin from address B to address C.
As long as the transaction made from address A to address B is unconfirmed, the transaction made from address B to address C can't be confirmed.

The two transactions that have been marked as "unconfirmed parent" can't be confirmed before confirmation of their parent.

Can you share your transactions IDs?
With sharing your transactions, you may hurt your privacy. But it won't have anything with your security.

An input that you used is unconfirmed. Check the transaction details and you'll realize that if you check the inputs of the transactions with unconfirmed parent, at least one of the input is unconfirmed.

Assume that you have sent bitcoin from address A to address B and then sent the same coin from address B to address C.
If you bump the fee of the transaction made from address A to address B, the transaction made from address B to address C becomes invalid.


The total virtual size of your transactions is 427 vbyte and the total fee paid for three transactions is 3953 satoshi.
This means that the effective fee rate is around 9 sat/vbyte.
Your transactions are now around 45 vMB from the the tip and you shouldn't expect them to be confirmed soon.

If you are in hurry, bump the fee of transaction 3.
Currently, for a fast confirmation, the fee of around 20 sat/vbyte is required.
Given the total size of your transactions are  427 vbytes, you should pay 8540 satoshi in total.
You have paid 2945 satoshi for the first two transactions and you need to pay 5595 satoshi for the third transaction. So, you need to bump its fee to 38 sat/vbtye.

Again, if you are not in hurry, just wait.

Edit:
I assumed that transaction 3 is spending the fund received in transaction 2 and transaction 2 is spending the fund received in transaction 1.

It can be both.

If there is an unconfirmed parent then you can use CPFP (Child Pays For Parent) meaning (more or less) that your transaction has a high enough fee that a miner will also mine one of the incoming (parent) transactions.

If you sent the transaction with a fee high enough that a miner will not want to include the parent then you have to wait.

If you do not have RBF (replace by fee) set to on then once you broadcast that transaction it's out there, you cannot add a larger fee to get it confirmed more quickly.

I'm on mobile so I can't see the images.

If you give the TXID others can probably help more.

-Dave

As far as I understand, you already have one unconfirmed transaction and you are trying to send another or the you have an incoming unconfirmed transaction and you are trying to send it while it's still unconfirmed?

Either way, you just need to wait for that unconfirmed transaction to get atleast 1 confirmation before you can send your balance. That yellow exclamation is a sign that the source of your funds is still not confirmed on blockchain.

The amount doesn't matter. Take the total fees of all of the transactions and divide by their size. For example:

If TX 1 is paying 1000 satoshis in fees, 300 bytes, TX 2 2000 satoshis in fees, 400 bytes, TX 3 4000 satoshis in fees, 400 bytes. Then the effective TX fees across all of the transactions would be 7000/1100: 6.3 satoshis/byte. If the result of your calculation isn't at least 12 satoshis/byte then you probably won't get a confirmation so soon.