Finally, 3 attempts later (after getting step by step guides, scripts, and pictures) of what was being asked.
So yeah, I guess I can now apologize for thinking you don't have the private key to that address.
I also guess you could have done this way earlier instead of engaging in e totally useless emotional roller-coaster. But I forgive you - you had no idea how to generate the hash, or of what to generate it. Or even why I asked it, lol. It's ok, bib.
But since you needed like several people to help you understand something so basic, it shows your extensive skills in hash functions, and more generally in how Bitcoin works. I mean, for the love of God, I fear you fail to understand what exactly you are searching in these puzzles, and why. You are just using some tools made by other people, without even knowing how they work.
Apology accepted. (You don't seem to like apologizing.

)
My friend, the problem here is that since my English is weak, I didn't understand why you wanted the sha256 converted version of the public key. lol
As I said, I know the hashing process.
My work is on hex and decimal.
I can calculate the AVERAGE PROBABILITY of which hex range the wallets are in with their prefixes.
For example; I found the 18th 1MVDYgVaSN prefix 45 minutes ago.
It would take months or years to scan all the ranges with my hardware.

That's why I'm focusing on the 1MVDYgVaSN prefixes. After it comes out in the range I calculated, I move on to the next one. To save time.
I already told him he wasted his time, energy & electricity. I think he finally got a reality check now 😂
As I wrote above, as a result of misunderstanding (because of my bad English)
KTimesG wanted - Sha256.Publickey
What I understood - Sha256 converted version of the Public Key.
Also, I said it before. I don't have any costs, the hardware works in the office I work in. The company accepting the work and calculations I do = cost-free work.