This is based from the auto-selected server's mempool.
If your Electrum auto-selected a new server where the previous transaction is kept, your wallet will remove the conflicting transaction and replace it with the one in their mempool.
This explanation has made me understood everything pertaining to auto-connection and manual de-selection .. I thought every single sever would automatically have the Tx as long as it was broadcasted.
To mitigate this (at least at your end), untick "Select server automatically" then manually select a server,
preferably those that support "full-rbf" since you're replacing a non-rbf flagged transaction.
(try electrum.blockstream.info:50002:s)
I actually -- out of more curiosity (not to get the funds off the mempool, but to understand the whole process) cancelled the transaction and realized that that was as good as broadcasting another transaction, waiting to be confirmed 🤦
So currently, I've got the first transaction with the 30 sat/vbyte waiting to be confirmed and also the same transaction waiting to be cancelled, also in the confirmation process but with a much lower fee rate.. I'm a mess!!!! But I'm happy that every bit of it isn't a waste cus I've definitely acquired alot of technical knowledge.
Y'all really helped...
I dunno what else to do now but maybe I'll just increase the fees of the cancelled transaction...if it's confirmed and cancelled, then I'll wait till whenever Edit; the cancelled transaction was on a higher fee rate; 50 sats/vbyte.
Note: The pending transaction is the same transaction I canceled..
With canceling a transaction in electrum, you replace it with a new one paying higher fee and sending the fund to one of your own addresses.
And @achow101, the great coderman once asked;
why's the technical part of Bitcoin so hard to understand?. I'll just bump double fees; if it gets the money exhausted, I'll just let it slide.. that's life.
Sandra 🧑🦰