Etherscan.io <http://etherscan.io/> is the ethereum network explorer where you can search transactions, see blocks, etc. I noticed that when I do a transaction that the hash generated is different than what i get from the RPC server and what shows up on the blockchain. My code is pretty much exactly as you show in your examples. I don’t want to share a working piece of code as I would be required to provide my private key. So I hope this helps. ## CODE EXAMPLE OF WHAT I AM USING use ethereum_tx_sign::LegacyTransaction; let new_transaction = LegacyTransaction { chain: 1, nonce: 0, to: Some([0; 20]), value: 1675538, gas_price: 250, gas: 21000, data: vec![/* contract code or other data */], } let ecdsa = new_transaction.ecdsa(&private_key_32_bytes); let transaction_bytes = new_transaction.sign(&ecdsa); let hash = new_transaction.hash(); ## ENDS HERE. The hash in this case that is generated at the end is incorrect. I have actually figured out to how to resolve this and get the correct hash if that helps. To do so, I have added the following to my rust code: use sha3::{Keccak256}; let mut hasher = Keccak256::new(); hasher.update(transaction_bytes.clone()); let hash = hasher.finalize(); With the following added, I am now able to get the correct hash from the transaction_bytes above. But perhaps there is a better way to do it without adding another crate since your using tiny keccak. I notice your example README that you do not have the transaction hash as part of it, but it is a function at: https://docs.rs/ethereum-tx-sign/6.1.3/ethereum_tx_sign/struct.LegacyTransaction.html Yet, the function doesn’t work as I think it should since it does not allow me to input the transaction bytes to generate the correct hash.

That would work, as long as there is a way to get the signed_hash() for us users of the crate whether thats the default or simply a library function. I can’t see any reason why anyone would ever need the unsigned_hash().