That is a 160-bit SHA-1 hash, calculated as specified by RFC 4880 § 12.2. Depending on how those bits hashed out, you perhaps may only have slightly more luck finding in it a minuscule RSA modulus plus public exponent than you would using RSA-512 to generate Bitcoin keys.
You keep making assumptions about what I am working on but i am not trying to talk to the Bitcoin
network and have some work to do with coordinators and
four way transactions that all need to be secure and I know this is strange but its windows based so I tend
to use the tools to hand and the 512 bit key your banging on about is not significant to me at this point in time.
it said
"The code I use for now in C# to create keys/Exponent is shown below" so put your glass on please.
Secp256k1 from what I can see does not allow encryption with the private key so it can be read with the public key
because the signature signing needs to encode something from the public key to work but it does offer some advantages
over RSA but i want you to know that I could not have managed to get this far without expert help from yourself