The Hash value of an ethereum and a  Bitcoin transaction is actually a PRIVATE KEY of an account.Hi, am Dennis Abari. While doing some analysis on ethereum virtual machine (EVM) , I discovered something quite interesting. The hash of an ethereum transaction is a private key. I later tried it on Bitcoin. The result was the same.  All this while, we have been staring at lots of private keys from different address transaction histories without taking note.To test my hypothesis more. I searched for top ETH account addresses by balance. I picked one of them. I search the address on etherscan.The ETH address search returned a log of all transaction history associated with the address. Each transaction had a hash.I took the hash, went to myetherwallet.com, clicked on access wallet, import using private key. I paste the hash from above and clicked on import. Boom. I got acesss to the wallet. Don't worry, the account balance was zero. The funds have already been sent to another wallet. (You can view that from the log of the transaction history I talk about early on).I also went to live.blockcypher.com to experiment. I took another ethereum address and searched. It returns a long list of transaction history. I clicked on advance details, API calls. It returned a JSON file. I scrolled down to "spent by" and "hash" values.I copied one of the "spent by value" and a hash value and opened my trust wallet. Clicked on I already have a wallet, import using private key.I paste one of the values from above and boom. I was in. I have gotten access to the account.I did the same for Bitcoin, I got access to all the account using the hash value (Private key).I searched for top ETH miners and used their address to get hashes too and got access to all I tried. It seems the hashes are accounts (private keys) that have done some transactions with that particular crypto address.Would appreciate your feedbacks on this. Experiment and tell me what you see.You can also hit me up via my personal email: {AbariDennis@outlook.com}