I forgot to mention that the tx measurement in mempool is
sat/vB. On the other hand, Mycelium's is in
sat/byte.
And it's clear to me now that these two are different units of measurement; byte is larger than the vbyte.
byte= vbytes * weight / 4
That's most likely the part where I got confused.
Did you check the version of your wallet? The current version is 3.16. For me the transaction fee for Normal is showing $23.94 and for Economic it is showing $17.43.
Mempool give you an approximate transaction fee value. If you want to replicate it then use Low priority wherein you will find a fee of $14.81
Yep, same version. I see that we got the same transaction fee displayed. Which tells me that there's nothing wrong.
Why don't use Electrum wallet which is available for mobile too?
One disadvantage, Mycelium wallet does not support Replace-by-Fee but they support Child-Pay-For-Parents. CPFP is more expensive than RBF but Mycelium wallet claims that they support a feature to Bump fee (but unfortunately it is CPFP, not RBF).
Bump-fee option (child-pays-for-parents algorithm)
I am aware of the priority levels, I still haven't chosen one though as I do not want to pay this much for now (and if ever I chose to lower the priority, it still got no guarantee that the tx will be confirmed in a short period of time). The reason why I'm still using the wallet is because I got used to it and I never had any issues. I'll consider hopping to Electrum, thanks!
There is a difference between mempool as been an explorer and the Bitcoin mempool where unconfirmed transactions are been received for miners to confirm, that been said.
Every wallet has a reference mining node where they take recommendation fees from, it is possible that the Mycelium wallet nodes is/are not connected to their mining node and that is why there is a disparity in your fees but I don't think it is something to worry about, you can set your fees in according to what you want it to be, you can increase it to medium or high priority, the main thing is for your transaction to be confirmed.
Yeah, it could be something related to the recommended fee, specifically, because
sats/byte does not include the
transaction weight which results in an overestimation of the fee. (Just realized it recently after a few Google searches). Thanks, man!