Safe Inspector
Inspect any Safe and verify every queued transaction hash.
Reads public data
Paste a Safe address to read owners, threshold and the pending queue.
About safe inspector
Owners, threshold, nonce and the pending queue for any Safe — with every queued transaction hash recomputed here rather than taken on trust. That distinction is the whole point. The service is trusted to say what is queued; it is not trusted to say what a transaction hashes to, because a compromised interface showing signers a legitimate-looking screen while they approve something else is exactly how the largest exchange hack on record was executed. Configuration is read from the Safe contract itself, so it cannot be misreported. Delegatecall in the queue is legitimate in batching, and also how a Safe gets emptied.
Common questions
How do I verify a Safe transaction before signing?
Compare the hash. This reads the owners, threshold and nonce from the Safe contract itself, then recomputes the hash of every queued transaction here and checks it against what the transaction service reports. A mismatch means the transaction was altered after it was proposed, or something between the proposer and this screen is not what it claims.
What is a delegatecall in a Safe transaction?
A delegatecall hands control of the Safe to another contract for the duration of the call, letting that contract act with the Safe's full authority. It is legitimate in batching, and it is also how a Safe gets drained — which is why one appearing in a queue you did not expect is flagged here.