22d63c93ae2e93c646c23630893b305b3536152dce4c9689ed8e25a42a431169If this is the parent transaction as nc50lc pointing you can do double-spend and rebuild the transaction. Doing this all child transactions will be rejected and you will need to pay a larger fee.
What I would like to know is if where is the another wallet where the BTC came from
This large output
So where did you create this transaction "22d63c93ae2e93c646c23630893b305b3536152dce4c9689ed8e25a42a431169" it was from segwit addresses and sent to legacy address. I can't find it in your screenshot where all of your output is in your transaction history.
Here's how to rebuild the transaction.
If you have control of these segwit addresses where the BTC came from(Outputs) then you can make a double spend or rebuild the transaction(Make new raw transaction) and reject the recent child transactions.
According to this
calculator the transaction size is 21948 bytes with 148 outputs and 1 input and the recommended fee right now is 170sat/byte but the Mempool keeps changing over time. So I suggest 200sat/byte if you are going to rebuild this transaction.
I do recommend go to this
https://mempool.space/ to know the recommended fee and use the high priority instead because the recommended fee is always changing every couple of minutes.
Use this tool
https://coinb.in/#newTransaction paste the parent transaction(TXID)
Now calculate the transaction fee 21948x200sat= 4,389,600 sats or 0.04389600 BTC or 43.896mbtc.
Now edit this part
it should be 0.04389600 fees before you submit
It should be like this
Now submit and it should generate a raw transaction copy the whole text and paste it to Electrum check the image below where to paste it.
Sign the transaction then broadcast.
And I hope this one will work and solve your issue just wait for a couple of minutes or maybe hours.