# How to calculate a hash of a Tx?

How does one calculate the hash of a Tx? Which fields need to be double SHA hashed and in what order?

-
Do you mean the transaction ID hash that the JSON-RPC send* methods return? It can be confusing because hashes for transactions are calculated and signed to transmit bitcoins, but the hashes that are signed are NOT the same as the transaction ID hashes.... – gavinandresen Dec 8 '11 at 3:32
I mean the hashes calculated for the merkle tree, but I suppose both would be useful. – ThePiachu Dec 8 '11 at 11:16

As explained by Gavin Andersen on the forum - in order to calculate the ID hash of the Tx that is used in the Merkle Tree, one needs to SHA hash the whole Tx message as defined in the Protocol Specification wiki page twice.

For example, for the only Tx from the Genesis Block one would double hash the following array of bytes:

01000000010000000000000000000000000000000000000000000000000000000000000000FFFFFFFF4D04FFFF001D0104455468652054696D65732030332F4A616E2F32303039204368616E63656C6C6F72206F6E206272696E6B206F66207365636F6E64206261696C6F757420666F722062616E6B73FFFFFFFF0100F2052A01000000434104678AFDB0FE5548271967F1A67130B7105CD6A828E03909A67962E0EA1F61DEB649F6BC3F4CEF38C4F35504E51EC112DE5C384DF7BA0B8D578A4C702B6BF11D5FAC00000000

And if double hashed correctly, it would give the following hash:

4A5E1E4BAAB89F3A32518A88C31BC87F618F76673E2CC77AB2127B7AFDEDA33B

-
Little endian! In most implementations that double-hash would yield `3b a3 ed fd 7a 7b 12 b2 7a c7 2c 3e 67 76 8f 61 7f c8 1b c3 88 8a 51 32 3a 9f b8 aa 4b 1e 5e 4a`, but you'll want to reverse that: `4a 5e 1e 4b aa b8 9f 3a 32 51 8a 88 c3 1b c8 7f 61 8f 76 67 3e 2c c7 7a b2 12 7b 7a fd ed a3 3b`, resulting in the actual hash that is actually used. – Kenan Sulayman Mar 7 at 0:42

There's a diagram explaining the process of hashing a transaction when creating or verifying the signature of a bitcoin transaction on the forum, and a higher resolution version of the same image on dropbox.

-