![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi114.fastpic.ru%2Fbig%2F2021%2F0317%2F37%2F01fe1adc0f755ad96cc407dfddff6037.png&t=662&c=utB9bsb2Jp5Y0Q)
That private key does not ended in the red bracket you used for demarcation. Also know that cryptography is wider, the example above like the one below is an '
Elliptical Curve Keys created using OpenSSL' not the way bitcoin private key is created. This is used in generating a self-signed certificate
https://www.scottbrady91.com/OpenSSL/Creating-Elliptical-Curve-Keys-using-OpenSSL-----BEGIN EC PRIVATE KEY-----
MHcCAQEEIKEubpBiHkZQYlORbCy8gGTz8tzrWsjBJA6GfFCrQ98coAoGCCqGSM49
AwEHoUQDQgAEOr6rMmRRNKuZuwws/hWwFTM6ECEEaJGGARCJUO4UfoURl8b4JThG
t8VDFKeR2i+ZxE+xh/wTBaJ/zvtSqZiNnQ==
-----END EC PRIVATE KEY-----
NotATether has commented about how bitcoin private keys looks like, the WIF-compressed starts with either K or L while the WIF starts with 5. To do that, bitaddress.org is enough. There is another type that is used to generate the WIF-compressed or WIF private key which are in hexadecimal, while the last one starts with 6P if you encrypt your private with BIP38 passphrase. But the wallet import formats start with 5, K or L. For low transaction fee, compressed private key should be used.