According to their native block explorer, you have received 94.818786 BCD: explorer.btcd.io/#/address?loading=true&address=12GWxyzArz5oSRmNsrTMQfjnYKbkoJKPjg
However, Electrum is a Bitcoin [BTC] wallet not a Bitcoin Diamond [BCD] wallet.

The good news is, you can export that address' private key from the addresses tab and import it to a BCD Electrum wallet;
Here are the steps:

• First, enable the 'Addresses' tab by using the menu "View->Show Addresses", then go to that tab.
• Find "12GWxyzArz5oSRmNsrTMQfjnYKbkoJKPjg" among the list and right-click on it.
• Select "Private key" and its private key should be displayed after typing the password, copy it.
• Download "Electrum BCD" from this link: www.bitcoindiamond.org/download/
• Open it, create a wallet but select "Import BitcoinDiamond addresses or private keys" when prompted for the wallet type, paste the private key and finish creating the wallet.

Are you pertaining to the balance in the the latest version where the private keys are imported?
If so and the connection icon is green (lower-right), then I'm afraid that those imported keys are really empty.

AFAIK, there's no other seed compatibility-breaking update after v0.34 so those are the only two versions that you can try.

I can't reproduce this since I don't have those versions installed, try to ask @ETFbitcoin if he can reproduce it to see what's happening.

You mean in the 'splash screen' before the GUI shows?

You might have to check the log to get an idea on what's happening under the hood, it's in bitcoin data directory.
If you set a custom datadir, it should be there, the file is "debug.log".

Against a random stranger, of course no.
Against something like what's being discussed in this topic (a recovery service), yes.

If you read the article, they have a website that offers crypto recovery service.

Nothing much in the errors, but that could indicate that your Blockchain is indeed pruned (as the other users suspected)
since Armory can't load it, the old blocks must have been deleted already.

Take note that you'll have to resync Bitcoin Core again after disabling that option, and it will require quite high storage space (400GB+).

Here's the link for version 0.32: https://github.com/spesmilo/electrum/tree/506eb41d91d9973fcae79a7db9ea64465203f4e3
Version 0.33: https://github.com/spesmilo/electrum/tree/ac918d02e626ec0fe8cb3b456162725d2988bf8e
Either of the two has the same key derivation update that's incompatible after 0.31 and before 0.34.

I'd suggest to use 0.32, install it the same way you installed 0.30.

Go to your electrum-0.30's folder and open 'client' folder, the file that you're looking for is "mnemonic.py";
open it as a text file and you should see the word list, however, there's no word "glamour" among the list, just the same list in pooya's link.

If the issue happens even if you have Bitcoin Core, you should share your logs (or just the error parts) for us to see what's happening.

You can get if from the file "Armorylog.txt" file in Armory's data directory.
The default datadir for Windows ("appdata" is hidden): C:\Users\<YOUR_USERNAME>\AppData\Roaming\Armory\

@dude1234321 May I ask, what's the goal in asking about the old version's key derivation? This might be an "XY problem" (wiki XY problem).

BTW, you can find Electrum's commits in the link below and browse the repository's state at that point by clicking "<>" at the right side of the commits.
The link is at the initial release, click "newer" for the later versions.
here: github.com/spesmilo/electrum/commits/master?after=baff4fa6259372b667042dae808123bfcb0f0964+13980&branch=master

There are too many versions before the seed phrase implementation, so you might be needing the link for your research.

According to the initial release, it is deterministic: github.com/spesmilo/electrum/tree/6db1a31e58ee15c448448139e7d3a9e72b14268f
But there's no description that it accepts private key, only "passphrase" that will be used as seed.

note: I haven't used the initial release so it's all based from the available data in the repository, some old-timers might have better answers.

I only see people doing this if it's their first time sending to a newly installed wallet; and some for high value transactions.
I mean, "see" as I remember users included it in their description in some technical support threads.

Anyhow, as mentioned, Electrum has such feature, except the broadcasted transaction could be mined in the next block before you can send the "double-spend" txn it if it has enough fee rate.
But still, the average of 10-minutes per block offers enough time in case the receiver didn't see the unconfirmed transaction or if it was sent to the wrong address.
Non-custodial wallets should be able to see the broadcasted unconfirmed transaction right away, no need to implement "step2" if that's your concern.

|

hosseinimr93 is correct.
You can confirm it by checking the latest (send) transaction's details in the history, right-click on it and select "View Transaction".
Under "Inputs (2)", there should be two entries that have the same TXID as the transactions from Coinbase and Localbitcoins.
It means that it spent the funds from those two transactions.

Seems like you have clicked "max" unintentionally?

Additionally, next time, if you want to use only one/specific input(s) (eg. only from Coinbase), utilize "coin control":
Enable the 'Coins' tab to view your available inputs (View->Show Coins), go to the 'Coins' tab, right-click and select 'Spend' on the input(s) that you want to spend.
It will display "coin control active" at the bottom and when you go to the send tab, it will only use the selected input(s).

I highly doubt it, Electrum will only require about 56MB of data once (first time it launched), then only a trickle of few bytes after that.
Unless you're running a few lightning channels without trampoline routing.

I don't get the point of the question,
is it in case the recovery service recovered the key from the wallet, spent the funds but told the owner that they failed?
If so, it's easy to tell if the funds were spent because the user can always check the funds through various blockexplorers or using a 'watch-only wallet' made from the bitcoin address.

If that happens, you can create a scam accusation thread with enough evidence like screenshots of the wallet and conversations, etc.
Most of the time, it's enough to crush a service's reputation if provided with strong evidence.

For the record, the delete option in the receive tab is labeled "delete", while the one in the history (only for local transactions) is labeled "Remove".
So since you've mentioned that you clicked "delete" in the OP, it's the receive tab which is only an invoice.

That also explains the "blank memory" of the sender because there wont be a sender if you haven't sent the invoice to anyone.

Yes, Bitcoin Core is a hard requirement of Armory.
Without it, there's no way for Armory to acquire the data from the Bitcoin blockchain.

Take note that you should disable the "prune blockchain" settings in Bitcoin Core before downloading the blockchain or it will not work with Armory.

Okay...
I see the situation strange based from the available info and at this point, I have no idea what's happening in your client since none of it should happen under normal circumstances.
('Imported' into 'imported watch-only' | Imported the same prvKey  to other wallets and derived different address)
Sorry I can't help more.

I think the information you need is about the nature of private keys and addresses.
It's not some sort of a backup that'll fetch an address from a server; just think of it as a "pair".
The Private key is actually a big number which a public key can be computed from, and the address is derived from that public key.

Better ELI5 explanation: https://learnmeabitcoin.com/beginners/keys_addresses

There can't be a network/server-side error which could lead to wrong address recovered from a private key, all is computed by the client/wallet, if there's an issue, it's the client.
With that, if Blockchain.com and Exodus both derive the same address (and test other clients), then there's something wrong with your Electrum or you've imported the wrong private key.
You said that you've verified its signature and it checks out?

BTW, your images: "Coin Control" and the alleged turned watch-only wallet "Electrum 2" doesn't fit the story because of the huge difference in the number of available (unspent) outputs and "TX" count in the history.

Yes.
BTW, what's the reason why you need to use another wallet? As another cosigner?
If so, that client should have a "PSBT" feature (Partially Signed Bitcoin Transaction), without it, it wont be able to sign the exported unsigned/partially-signed transactions from Electrum and vice versa.

Problem is "Coinbase" isn't "Coinbase Wallet"; although both are products by the same company, those aren't the same.
OP's wallet is the latter which isn't custodial, so Coinbase doesn't have anything give him since they don't have the funds.

BTW, if you've read the previous replies, you'll see that in various users' attempts, they can restore their address in Electrum,
but for some reason, OP can't (and it's for you to judge what went wrong).