Verify a Safe Transaction Hash

What this tool does, and does not, tell you

It does not tell you a transaction is safe to sign. It only recomputes the hash from the same raw parameters the Safe front end used to build the signing request, so you have an independent value to compare against your hardware wallet's screen.

• Your hardware wallet computes its own hash from whatever the connected app sends it. If that app is compromised, the wallet screen and this tool can both be shown correct-looking data that does not match the transaction actually being proposed: always re-check the to, value, and data fields below too, not only the final hash.
• Compare the domain hash and message hash individually if your device shows them separately, then the final Safe transaction hash. If any single hex character differs anywhere, stop and do not sign.
• It follows the approach of the open-source safe-tx-hashes-util by pcaversaccio: the same hashes, and the same warnings for an untrusted DelegateCall, a custom gas token or refund receiver, and a change to the Safe's owners or threshold (also inside a multiSend batch). A hash match with a warning still means the transaction can do exactly what the warning says.