You see where I am going with this?
yeah but i still find hexadecimal representation more confusing than at least working with bytes (base-256).
It's always evolving with each input and it's just assumption that it will successful know all the input that was there in the past for a specific seed.
you use the word "know" but knowing comes from either having it stored in memory to look it up or have the capability to compute a ton of hashes to find a collision.
notice that i said collision, since you can never know the message that was hashed ever even if you could find another message that produces the same hash.
Or may be I need to read more before I can know I am predicting it right.
maybe search a little about different attacks against hash algorithms like preimage and second preimage attack which seems to be what you are describing here.
But, it will reveal identity of every transaction that happened in the past. Lets say BTC transaction may be.
what do you mean by "identity of every transaction"? SHA256 is not used to hide anything in a transaction. the only thing that you may have been thinking of is the public key or the scripts that are hashed: alongside RIPEMD160 for P2PKH and P2SH and P2WPKH scripts and a single SHA256 for P2WSH scripts. but even if you were able to reverse that (which will always be impossible) you are still left with a public key or a script that requires breaking ECDSA too.