Since it's still unconfirmed in Electrum, the chosen server still has it in their mempool, you can't remove it and send another that spends the same input while it's like that.
As we speak, the purging fee rate recovered below 5sat/vB, but it wont stay like that.

I can't see any new unconfirmed transaction in the link in the Edit.
Have you sent using Trustwallet?
If so, your transaction may have been rejected by majority of the nodes for being a replacement of a non-rbf txn, since it didn't propagate.
It'll only be accepted by nodes with full-rbf option enabled, but it's currently the minority.

-edit-
As expected, your old 5sat/vB transaction reappeared in that link.

I take that it "reversed" in your Trust wallet, right?
The current default mempool size exceeds the size which transactions with 5sat/vB and below got dropped, yours included.
But some nodes still have it, so it might propagate again when the default purging fee rate lowers again.

This is the right time that I'm talking about in my post.
You may need to spend it right now.

Although this sounds plausible, using a custodial client isn't really going to increase your privacy.
As per Moon's privacy policy, they keep logs on almost everything you do with their service "in case of an error".
More info here: muun.com/privacy_policy.html and muun.com/privacy_policy.html#service_providers

If you want privacy, use a non-custodial Lightning wallet which doesn't rely on third-party to manage your channels.
It's a plus if you can connect your own node to it and can connect through Tor.

Addresses are just encoding of the HASH160 of the public key, it's not something special that can be a solution to the puzzle.

Since puzzle #66's output contains its hash160 which is 20d45a6a762535700ce9e0b216e31994335db8a5, you can just derive the other address types from it.
You can even decode the address and derive other address types from it.

From HASH160, it's as simple as this:

• HASH160 of its pubKey: 20d45a6a762535700ce9e0b216e31994335db8a5
• Prepend OP_0 and size '0x14': 001420d45a6a762535700ce9e0b216e31994335db8a5
• HASH160 of the above: f0a433b3411b7c1812937977bebd25602f55b68f
• Prepend the version byte '0x05': 05f0a433b3411b7c1812937977bebd25602f55b68f
• Append the checksum: 05f0a433b3411b7c1812937977bebd25602f55b68f31c18fc0
• Encode to Base58: 3PdQoXyQwWmerpt3SbF7Hbh3aukC5w28GP

Try Blockcypher's API.
Their blockexplorer has a simple "x hours/days/months ago" message but the API call for "txs" has 'received' timestamp which is when they've received the transaction into their mempool.

For example: https://api.blockcypher.com/v1/btc/main/txs/29dd0ce748f0489d1aece0282f2b2031fcb31fbdf0d70fece99e56fc5702a6e5?

He already saw the main screen and still thought that it's not watch only.
Reading the literal "watch only" text should get him at ease that it's actual watching-only wallet.

The 'Send' tab will only allow you to create a PSBT without any signature, it wont continue to broadcast an unsigned transaction.

In Android, you can check the wallet's type by tapping: "<Wallet name> -> Wallet details".
You should see a "Watch only" tag with an 'eye icon' above the screen below 'Wallet details'.

Wasn't BlockFi already bankrupt?
I've checked the content of the FAQ link in the second screenshot and it seems their withdrawal process requires more than just an address.
Read the contents here: https://blockfi.com/wallet-withdrawal-faqs
If you haven't' completed the identity verification emailed to you, that must be the reason why they still haven't processed your withdrawal.

As for Electrum, enable Electrum's 'Addresses' tab in them menu: "View->Show Addresses", then open it.
See if the address that you've used to withdraw is in the list (check every characters);
If so, your bitcoins will be received by Electrum once BlockFi initiated the withdrawal.

There's a lot of criteria and ban score based from the severity of its misbehavior.

For that, you'll need to check it directly on the code, "new_processing.cpp": https://github.com/bitcoin/bitcoin/blob/master/src/net_processing.cpp#L539-L543
The linked line and comments show "howmuch" ban score to add to a misbehaving peer.
Search for "misbehaving(" on that link to check all the scores and reasons, the developers conveniently added comments to explain each.

Okay, but since I've provided you puzzle #66's partial WIF, go and solve it quickly now.

I'm "nicely" asking if you just mistyped since having access to the unsolved puzzles' public keys makes more sense than getting their partial WIF.
If that's not what you mean, you must be misunderstanding the few other posts that you've replied to.

regards,

You mean the unsolved puzzle output's "Public Key" right? not partial WIF.
Because otherwise this wont make any sense.

And BTW, specific puzzle output's partial WIF should be similar to the closest solved outputs' WIF since they're all encoded starting from bunch of zeroes.
Like #66's partial WIF, which should be: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3.......
Based from:

• #65: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZM21gaY8WN2CdwnTG57
• #64: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZ6FxoaD5r1kYegmtbaT
• #63: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYv5Z9J7hv7VYYN3XL3Y
• #62: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYpCemuaUp7NigjvtJug
• #61: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYmLDHsih379uP9zbHSD

You can restore it to the latest version and synchronize the blockchain or export your private key(s) and import them to another wallet.

For the latter, here's a simplified instructions on how to export the private key(s) from Armory: https://bitcointalk.org/index.php?topic=5233141.msg54037227#msg54037227
But for security purposes, I suggest you to verify Electrum: https://bitcoinelectrum.com/how-to-verify-your-electrum-download/
And you may consider restoring the private key(s) on an Air-Gap machine, more info: https://bitcoinelectrum.com/creating-a-cold-storage-wallet-in-electrum/

learnmeabitcoin has a beginner and technical articles regarding 'target' and 'difficulty'.

The explanation in the beginner page should be enough to explain how difficulty works: https://learnmeabitcoin.com/beginners/difficulty
After that, go to the technical part for more information about the target: https://learnmeabitcoin.com/technical/target

Clients take xpubs differently:

• Some have specified extended public/private key format per script type like "xpub", "ypub" and "zpub" which indicate the script type of the addresses to be derived.
  Like I've mentioned in the very first reply, Electrum take an xpub as indication to derive standard (P2PKH) addresses from it.
  Blue Wallet isn't strict on this when importing a master key but new addresses will default to whatever the format of the imported xpub.
• Some clients only take the "xpub" format and have their own way of identifying/setting the script type of the addresses to be derived.
  Like for example, Sparrow which uses descriptors.

So based from your latest replies, I think when you imported it to Blue Wallet,
it automatically detected your existing transactions which are for your native SegWit addresses and created a wallet based from it.
But when you requested a new address, since you've imported an "xpub" instead of "zpub" it gave you legacy address type which didn't yet exist in you Ledger Live.

Periodically, maybe some clients.
Nodes? AFAIK, Bitcoin Core is known to rebroadcast wallet transactions and the contents of mempool.dat during startup, but I'm not sure if it does periodically.

Anyways, as what I've observed, OP's transaction was once missing from some mempools (e.g.: missing in blockchain.com blockexplorer) and just became available automatically hours later.
And I've seen some unconfirmed Electrum transactions that became "Local" once it gets dropped from the selected server's mempool.

Yes, it's rebroadcasted/propagated since mempools just got lower in size.
That's why he should be at least active to check the purging size so he can have a chance to replace the transaction.

@SmartGold01 be sure to send a replacement with high fee rate right after removing the transaction after it turned "Local".
You have no other option aside from what I've posted in page1.

An hour ago, your transaction was purged from nodes with default mempool size configuration.
That's the best timing when you can replace it with a higher fee rate transaction.

If you're lucky, time it when the purging fee rate is higher than your txn's fee rate when your transaction was dropped from majority of the mempools including some Electrum servers.
You can check the default "Purging" fee rate in mempool.space.

When that time comes:
Restart Electrum and check if the transaction's status changed from "unconfirmed" into "Local"; if not, select another server.
Then after turning into "local", Right-click on it and select "Remove", then your coins should be available to spend on a new transaction.

My immediate guess is the copied xpub isn't related to any of your account in Ledger Live.
It can also be something like extended derivation done by Blue wallet to the provided xpub or as simple as different address type.
The worst case scenario is if it's changed from your clipboard by a malware.

As for Electrum, it derives the 'internal chain' and 'external chain' paths after the provided xpub,
for example: your_xpub/0/receiving_address_0+ & your_xpub/1/change_address_0+
In Electrum, the script type for "xpub" is standard P2PKH; in Sparrow, it depends on what you've selected.

Describe how you set-up your Ledger Device, the exact steps including the software used and which part of the client you've exported the xpub.

You can also tell how you imported the xpub to Blue wallet because AFAIK, Blue Wallet follows whatever path where it found any related transactions.
If it didn't find any, it wont let you import the extended master public key.

Hope this provided enough hint before clarifications are provided.

Since he didn't specified the wallet type and nobody provided instructions to create a watching-only version of a 2fa wallet, I've posted it just in case.

If his wallet is 2fa, it's exactly what he's looking for.
BTW, the wallet that'll be created will be "2of3, watching only" and not "2fa"; but it can generate the same addresses from his 2fa wallet.

Yes, but the steps depends on your wallet type.

If you have Standard wallet, doing what others said is the precise way to do this.
If you have a 2FA wallet, you'll have to restore a 2-of-3 Multi-Signature wallet containing all three master public keys (keystore1, 2 , 3) from your wallet information.
The order of the master keys doesn't matter in Electrum.