Quote from: Old and tired on September 30, 2024, 06:54:59 AM

Converting the hexadecimal to uncompressed and compressed wif was of course not an issue and using "importprivkey" and "rescanblockchain" in Bitcoin Core also easy.
After a full rescan in Bitcoin Core 25.2 the result was nada, zilch and nothing! Most likely these hexadecimal have nil purpose, but as I knew my uncle and he would not have saved this paper unless a good reason (unless he wanted me to chase ghosts!)

For that, please elaborate the steps that you've done or tools that you've used to encode your suspected Private Keys to WIF
so we can confirm if it's done correctly or if it's what caused the negative scan result.

Even if you've easily done it, it's best to have a second opinion on the accuracy of the procedures.

Quote from: Cricktor on September 30, 2024, 02:16:19 PM

I wonder a bit why someone would store private keys in hex format which is a rather error prone format.

Back when WIF isn't introduced yet (included in #574), some third-party scripts/tool exports prvKeys in HEX.
The only chance that OP's list are prvKeys is if it's older than that commit, else, it's as the majority said.