SSH public key verification with FingerprintHash

Whenever I'm connecting to a new remote server via SSH, I tend to verify the fingerprint to make sure that I'm actually connecting to my own machine. Usually it's not that big a deal as I'm simply comparing two strings, but what if those two strings are created with two different hashing algorithms?

This is what I saw today when I connected to a new server for the first time.

notebook $ ssh remoteserver.name
The authenticity of host 'remoteserver.name' can't be established.
ECDSA key fingerprint is SHA256:2weq/LEmJ77j6sJUV6krRPnA9KUqgoojH+uM0hOcOJY.
Are you sure you want to continue connecting (yes/no)?

Ok, instead of just typing yes, let's verify that real quick. To do that, I ssh'd into the hypervisor and connected to the server via direct console.
Now there are three ways I know of, how to verify the key, all of which boil down to string comparison. The question is, how to generate the string.

Looks like the same, however that's not really a convenient way to do things. There is one other way I can think of. Remember the FingerprintHash function I tried earlier? We can use it on the newer client to downgrade the fingerprinting to md5 and compare that with the servers key-gen result.