That's the "dbLog.txt" not "Armorylog.txt" but it looks like Armory is working fine aside from an issue with getting a transaction data from bitcoin core's mempool.

Have you followed goatpig's advice to start bitcoind with -server parameter? (post link)
Alternatively, you can add server=1 to Bitcoin Core's bitcoin.conf file in the default bitcoin data directory (location).

You need to paste the Armorylog to find the root of the issue, you can get it from "File->Export Log File".
And if it's too long, you can use https://pastebin.com/ and link that to your post.
(you can censor info like PC username and data directories if you prefer)

My guess is it could be a issue on your Armory database.
If that's the case, it's easy to fix but it's best to check the logs to be sure.

You can also paste the transaction ID to blockexplorers (like https://blockstream.info/) to check if the transaction already went through.
You can get the transaction ID from: Double-click the transaction, the "Transaction ID" is above the txn info.

Oh, I don't know if it's you or me who've successfully submitted it 
Anyways, it's now in their queue so even if the average mempool doesn't get better, your transaction can get a confirmation once ViaBTC mined a block like I've explained above.

Guess he fell asleep because it's still not in ViaBTC's free accelerator queue:



If it is, there'll be a message below the TXID saying "This transaction is being accelerated."
You can do it yourself though, paste the TXID and submit it "for free" in https://www.viabtc.com/tools/txaccelerator/ at exactly HH:00 during the very first few seconds and it should be accepted if your internet is fast.
Paste it again if it returned with an error since their server can't handle the surge of txn submissions, the message above will show if it was accepted.

Lastly, it wont be "accelerated" right away, ViaBTC need to mine a block or more first to include your transaction, so it depends on their luck and the number of queued transactions.
I'll try it too if I'm available, I'll inform you later if I succeeded.

--update--

Now it's in their queue:

Recently there was one pool that accepted a non-standard transaction and was successfully mined but it came with a bounty.
Here's the user's/pool's post: https://bitcointalk.org/index.php?topic=5192454.msg55842508#msg55842508

There's only listtransactions in bitcoin core but it's a wallet RPC.

If it's for a simple query, not a for a project, you can import it to a 'disabled private key' - 'blank wallet' as a watch-only address. (createwallet | importaddress),
after rescan, you can use the command to list the transactions of that address, through:(https://bitcoincore.org/en/doc/0.21.0/rpc/wallet/listtransactions/)

In contrary with the previous posts, your "unconfirmed" transaction turned "local" is because your selected server's node had purged your transaction from their mempool due to prioritizing txns with higher fee rates.
Then it returned to your wallet after either auto-connecting to a different server that has your transaction or it was re-accepted by their node.

70sat/vB is good enough IMO if you're not in a hurry. It's just because the average mempool is absurdly too high right now that a txn with good fee rate like that got stuck.
You can also try to accelerate it using ViaBTC's free accelerator, send it to them at exactly HH:00 in the clock.

There's a documentary specifically written for that purpose: https://github.com/bitcoin/bitcoin/blob/master/doc/reduce-memory.md
But seeing that you've already tweaked most of the mentioned configurations, it's only -maxmempool=<n> that you're missing.

Have you restarted the node after adding the configurations? Because you have to.

Are you looking at some specific blocks? If there's only a few, you should get their blockhash and use that as an additional parameter for getrawtransaction.
That should speed things up.

https://bitcoincore.org/en/doc/0.21.0/rpc/rawtransactions/getrawtransaction/

Electrum will default with mBTC unit which is equivalent to 0.001 BTC, in your case, you've actually sent 550 satoshi (0.00000550 BTC) as the previous posts mentioned.
You can change the base unit into 'BTC' in the settings if you want: "Tools->Preference->'General' tab->Base Unit".

The error you've received is because the total fee is much higher than the amount to be sent:

You might have dumped the wrong wallet, in CLI, you'll have to specifically load and indicate a wallet together with your commands.
Without loading other wallets, it will select the default wallet when using wallet commands.

Use this to load a wallet:
Use this to issue commands for that wallet:

Also, do you have any configurations in your bitcoin.conf file?

Looks like a payment invoice to me, sort of an invoice you've "initiated" to pay something, the clue must be in the reference.
So whether if it's paid or not, the bitcoin wasn't going into your wallet, it's outbound.

You can check the Bitcoin address on a blockexplorer to check for transactions, paste it on a blockexplorer: https://blockstream.info/
But that can only tell if you've paid the invoice or not.

Can I ask which kind of "Bitcoin" is it? You might have bought the wrong one.
Because Bitpay and Bitcoin.com wallets both support [BCH] Bitcoin Cash and [BTC] Bitcoin, while Electrum only supports Bitcoin.

If it is BCH, restore it to this fork of Electrum instead: https://electroncash.org/

Let it finish and if there's really no balance, then it must be an empty wallet.dat.

I don't think the private keys can be viewed in plain text, only the previously used addresses.
You can export the private key if you already know the address, use the command ("open console: Window->Console"):
and import that to Electrum using the 'new wallet' option "Import Bitcoin addresses or private keys".

Maybe... try to launch it "As Administrator', if it didn't worked, add an exception to your Antivirus.

Yes, after rescan, the wallet's correct balance should appear.
"pruned" is when you set the option (Settings->Options->Prune block storage to:) or in bitcoin.conf file to automatically delete the older blocks to save disk space, it has its ups and downs like rescan wont be available.

Ah, that's called "Sweep" but will not pay from Multibit, you'll just paste the keys to a new/existing Electrum wallet and it will create a transaction for you that'll send all of the key's available balance.
You can also "Import" the keys and it will create a wallet based from those keys.

Those non-custodial wallets aren't accounts, they only contain the necessary keys to spend your coins that's contained in the Blockchain.
What you need to export from Multibit are your "private keys" which I believe was already discussed in one of the threads in the linked board.

There's a "wallet.dat" in Bitcoin core's data directory (not the installation directory), here's the default locations: https://en.bitcoin.it/wiki/Data_directory#Default_Location
If your Bitcoin core is pruned, changing/loading another wallet might not work depending on pruned blocks; if it's not synced, you won't see any balance right away.

You might have pasted the wallet.dat file in the wrong directory. Bitcoin core wallet file's default name is "wallet.dat" (extension should be '.dat').

The wallet file isn't for Electrum nor Bitpay so it will not work, it's actually surprising that both clients asked for a password.
Note: Electrum's wallet name can be "electrum.dat" (old) or "default_wallet" and "wallet_1" the new version can be renamed and has no extension.

This will only make the already-generated next-19 receiving addresses out of your new gap limit (with red highlight).
But that wont stop the receive tab from changing the address when creating new invoices while there are still non-expired ones, it will still use the next address for the next invoice.

What will change is when you've used the last address, Electrum will only derive one more key pair (=one address) instead of 20.

"wallet.dat" must be Bitcoin core's wallet file, you can try to load a copy of it into an existing or new installation of Bitcoin core to check if it has any balance.
New installation will require you some bandwidth and disk space (300Gb+, you can prune it to reduce disk space usage).

You can also open a copy of the wallet.dat using a text editor and find (CTRL+F) lines with "name" on it, there should be an address next to them and paste those to a blockexplorer to check its balance.
Blockexplorer example: https://blockstream.info/ | https://blockchair.com/

What's the name of those "newer programs"?
Please be careful on using third party tools, some of them are designed to steal your funds.

Try to look for a related topic in this board: Bitcoin Forum > Other > Archival > MultiBit

Be wary of users who'll try to help you through personal message, do not share any info specially "keys";
and keep the discussion public as much as possible.

I believe you can extract your private keys from Multibit Classic but I haven't used it so I pointed you to the correct board.

5x10 with three colors... Maybe you're supposed to take the SHA-256 hash of the images and use the hash as a private key.

Also, it looks familiar, not Bitcoin-related but for an old game, but I can't remember which.