No worries.
I've noticed that it's written exactly the same in your other thread, I thought it was just a typo when typing that reply.
That's why I didn't mentioned it.

You only need the Native SegWit wallet since the address is native segwit.

If it's the first time you've installed Electrum, you'll need to wait for it to download the "blockchain headers" before it can display your correct balance.
That may take a few minutes depending on your internet connection (it's 54mb of data BTW, just keep it open).

AFAIK, specifically, "estimatesmartfee" is using the transactions in the node's mempool, the "estimate mode" just changes the history range to consider.
The other fee estimation command, "estimaterawfee" uses both mempool and blocks transactions in the estimation. [CMIIAW]

You should use the portable version or run it as portable (-P) because the stand-alone will use the default data directory.
The portable will use the flash drive as the data directory: "electrum_data" folder where the executable is.

I have no idea about the error, but it's not exclusive to electrum and it may have been corrupted during the transfer.

This is simply because not all nodes have the exact same mempool.
And mostly all of these estimators are based from their node's mempool, some are considering the last few blocks.

So even if it's based from "estimatesmartfee", you'll likely get a different results.
Moreover, the sites that you've motioned likely have their own algorithm on estimating transaction fee.

I don't know your code but try to see what went wrong by checking the difference between yours and this simple (working) python-bitcoinrpc script.
for Regtest:

If you want to share the "signed raw transaction" hex, it will be easy to tell what's wrong with the transaction just by looking at the inputs.
Note: that will enable the public to see what address(es) you're trying to spend from and to; as well as the inputs' public key. But they wont be able to spend from it.

Like this for example: Issue: mandatory-script-verify-flag-failed (Public key is neither compressed or uncompressed) #21098
Where the inputs' ScriptSig doesn't contain the public key, the signature is followed by 0x00 instead of the pubic key.

Seems like your wallet is having trouble constructing the transaction correctly.
If you can export the address(es)' private key(s) and import it to a reputable wallet, you can try to create the transaction there.
According to the IOS link of the app (is this the right app?), it's a non-custodial wallet and the private key is written in plain sight in one of the screenshot.

If it is.
You can download Electrum for PC (electrum.org), verify its signature (instructions) for safety:

• Install/Launch it and during wallet creation, use the option: "Import bitcoin address or private key".
• Paste the private key(s) of your address(es) and create the wallet, one prvKey per line if there's more than one.
• Wait for a few minutes to download the blockheaders and the balance should update.
• Then you can create a new transaction in the send tab.

Please take your time to verify your downloaded electrum's signature and make sure that the PC where you'll install it is secure.
If the amount is quite high, you can use the "cold-storage" option which requires a few more steps.

The source of the binary is at least from electrum's official website and the hash matches from the source.
Lines 74-78: https://github.com/flathub/org.electrum.electrum/blob/master/org.electrum.electrum.json#L74-L78
However, there are lot of other requirements from "python3-requirements-binaries.json", "python3-requirements.json", "python3-requirements-hw.json" alongside the installation which you can check if something shouldn't be there (most checks out BTW).

But please don't take this as a vouch

There are newbies who are "nuked" but most are just "banned",
a user's posts can still be active if it's the latter and the specific post didn't broken any rules or it wasn't reported yet.

The difference between the two are:

• Nuke - Deletes all the user's posts and ban the user.
• Ban - As you know it, forbids the user to use the forum but keep his posting history.

See the mod log for nuked user entries and click on the profile links to see their post history which are empty.

Where did you get those?
The blockexplorer "Blockchair" supports 17 blockchains but your transaction hashes neither belong to any of those.

The 'change address' setting is saved in the wallet file itself.
You can see it as the line: "use_change": true, if the wallet file isn't encrypted.
The other settings however is saved in a file named "config" in the data directory.

So if you want to see the default for that particular setting, create a new sample unencrypted wallet and see what's in the setting.
Spoiler: it's enabled by default.

The checkbox in proxy setting: "Use Tor proxy at port 9050/9150" will appear only if Tor or Tor browser is running and connected to the Tor network.
It will instantly appear/disappear when you're connected/disconnected to Tor network:


And you still haven't checked the logs to see if you can find an entry related to the re-sync issue.
You don't have to post them if you don't want to, just check the logs for errors.

I stopped using Coinbase years ago but as I can recall, I didn't received any random transactions
and it's highly unlikely that anyone would experience that unless it's the usual "dust deanonymization attack" (dust attack info).
But the amounts you've been receiving look like considerably good amounts and the usual targets are mostly already known addresses.

Other than those two that I've mentioned (plus the possibility of a fake wallet), I don't have any other idea where those transaction are coming from.

You must also consider the brands and models of your GPUs.
Different Video cards have different "normal" temperature range when in use, it may be hot but it could be a safe range for your GPU.

Maybe you have referrals in "Coinbase Earn"?
Here's the help center article about it: Coinbase Help Center->Getting started->Coinbase Earn

But if you're positive that you shouldn't be receiving any transactions, then start investigating if you're really using Coinbase app
and not a fake app where a scammer is in control of the wallet and just waiting for you to deposit a relatively large amount.
These are the links to the correct app:

• Android: https://play.google.com/store/apps/details?id=com.coinbase.android
• IOS: https://apps.apple.com/us/app/coinbase-buy-sell-bitcoin/id886427730

Are those being received from the same address?
I'm thinking that you may have left the address as a withdrawal address on a 'BTC faucet'
or an 'altcoin mining service that pays in BTC' that has auto-withdrawal feature and it may be profit from your referral(s).

I can't think of any other passive BTC income that a user can forget that easily.

Electrum is safe as long as the wallet is created in a safe environment and the secrets are safely imported. (also follow the link in Charles' reply)
For address reuse, regardless of the privacy issue, you've been using the same address before so there'll be no difference if you continue to use it again.

If you want to reuse it, use the option "Import bitcoin addresses or private keys" when creating a wallet.
The "Private key" option of an existing wallet in "Wallet->Private keys" will only enable you to sweep the address' funds.
But a new standard wallet with new seed is recommended.

I have Mycelium installed before upgrading my phone into Android11 and it did crash after typing my pin.
But after updating the app to version 3.10.0.3 from Playstore, it works without issues.

If you saved your "12-words backup", you'll be able to restore your HD account associated with that backup.

I'd suggest you to create your own topic if you came across an issue with the recovered wallet.

To start a new topic: click the board where you want to post it: Bitcoin Forum > Bitcoin > Bitcoin Technical Support
Then click "new topic" button at the left side of the screen ("CTRL+F" to search if you cant see it).

Enabling logging may give you a hint on why it's synchronizing when not needed.

You can enable it in:  "Tools->Preference->Write logs to file"
And the log file will be saved in: <electrum data directory>/logs