Before signing · while queued · after execution
Review a Safe transaction at every stage.
Inspect a proposal before signing, or investigate what an executed transaction did. Start with a Safe hash, execution hash, address, URL, or JSON.
A compromised multisig interface can describe one action while presenting different data for approval. Inspect the calls before signing, compare the hash on your signing device, and review execution evidence afterward.
Start with anything you have
Exported transaction JSON can be decoded without a Safe API key. An execution hash needs a working RPC; a pending Safe hash needs a proposal source.
How it works
One review connects the source of the transaction, a fresh Safe hash calculation, decoded calls, target code, and measured effects when available.
- Your inputSafe transaction hash
A hash alone contains no chain ID, Safe address, or calldata.
- Recover fieldsOffchain proposal source
Safe Transaction Service supplies the transaction if it has indexed it. A pending hash needs a proposal source.
- Our checkRecalculate and compare
Compute EIP-712 locally from those fields. When available, ask the Safe contract through RPC for its hash.
- ReviewCalls, code, effects
Decode nested calls; check target code and show simulation changes only when measured.
If Safe supplies both the fields and the reference hash, a matching hash proves consistency, not that Safe supplied truthful fields. Compare the hash shown on your signing device.
- Your inputOnchain execution hash
Select a network if the hash alone cannot identify it.
- Recover fieldsRPC execution and calldata
Read the transaction, receipt, and Safe execution event from the chain; reconstruct the Safe transaction.
- Our checkRecalculate and compare
Compute EIP-712 locally and compare the event hash. Query the Safe contract at the earlier block when archive state exists.
- ReviewCalls, code, effects
Decode calls and inspect code at execution time where the RPC and verified source allow it.
This path does not need Safe Transaction Service to reconstruct an executed transaction. Its independence depends on the RPC you trust; historical checks need archive state.
- Your inputSafe address or URL
A Safe URL supplies the chain. An address alone can exist on several chains.
- Find transactionsQueue and history
Where supported, Safe Transaction Service lists proposals and executions. Choose one transaction.
- Our checkRecalculate each selected hash
Read its full fields, compute EIP-712 locally, and attempt the separate Safe contract RPC check.
- ReviewCalls, code, effects
Show the decoded call path and the evidence still missing for that transaction.
A Safe address is a discovery input, not proof of what was signed. If the offchain queue is unavailable, this service cannot invent pending proposals from RPC.
- Your inputTransaction JSON
Use a complete Safe export, including the Safe, chain, nonce, and transaction fields.
- Recover fieldsYour file, parsed as data
Those fields do not need Safe Transaction Service. A Builder plan without a nonce is shown as a plan.
- Our checkRecalculate EIP-712
Compute the Safe hash without calling Safe Transaction Service. Compare a separately supplied reference hash and, where possible, the Safe contract via RPC.
- ReviewCalls, code, effects
Decode nested calls and mark code checks or simulation as unavailable when they cannot run.
An imported file can itself be wrong. Check its origin and compare the calculated hash with your signing device before approving anything.
Hash calculation is independent of the Safe API; the truth of input fields is a separate question. A compromised Safe service could return altered fields and a matching hash. Use a hash obtained independently, your signing device, and onchain evidence where available. No single service or simulation proves a transaction is safe.
Coverage
Network coverage by capability
These are the 13 named EVM networks with configured RPC routes. A matching chain ID confirms only that an RPC answered. Safe queue and history lookup, transaction reconstruction, historical code verification, and simulation are separate checks. The dated status below shows which Safe list endpoints answered; Amoy and Immutable zkEVM currently need an execution hash or supplied JSON because their Safe list endpoints are unavailable. Try a real transaction to see which evidence its providers can return. Other EVM chain IDs can be attempted without a promise of offchain discovery.
Network coverage snapshot unavailable.
Ethereum
Polygon
Gnosis
Arbitrum
Optimism
Base
BNB Chain
Avalanche
Katana
X Layer
SepoliaTry a transaction by network
Loading verified examples…
Community funded
Help keep reviews free
Donations help pay for the infrastructure behind this service: hosting, bandwidth, monitoring, transaction lookups, historical RPC reads, and simulations. Thank you for supporting independent review.
Sponsor recognition
Put your name behind safer signing
Diamond, Gold, Silver, and Bronze spaces have room for multiple sponsors. We also welcome infrastructure contributions such as RPC and simulation capacity. Recognition requires agreement before listing.
Ask about sponsorship on X ↗Use the evidence, verify independently
Safe Tx Lens is an independent community project, not affiliated with or endorsed by Safe or the Safe Ecosystem Foundation. It is free software with MIT-licensed source available on GitHub. Its data and analysis can be incomplete, outdated, or incorrect. It offers no guarantee that a transaction is safe and its maintainers accept no responsibility for decisions made from its output. Check the hash on your signing device, use independent sources, and review the contract behavior yourself.
For control over the code, keys, RPCs, and logs, deploy your own instance. If you find an error, report it on GitHub with public, non-sensitive details.