Tool selection guide
Transaction simulation tools: preserve state and inspect effects
A transaction preview is conditional on state and inputs. Decide whether you are predicting a proposed transaction, reconstructing an executed one or inspecting a trace. Keep the original block context and every override visible so another reviewer can distinguish observed chain state from your experiment.
Sources checked . Product documentation reviewed; no account, paid API or live transaction was tested.
Review what a buy-sell simulation can miss.
Decide what your review needs
- Record the chain and block context. "Latest" is a moving input and makes later reproduction harder.
- Keep sender, destination, calldata and value with the result. For a bundle, preserve the order and intermediate state.
- Disclose balance, storage and code overrides. A successful overridden run does not describe the untouched deployed system.
- Inspect asset movements and authorization alongside the success flag. A transaction can execute successfully and still do something the signer did not intend.
Compare inputs, results and limits
| Tool & access | Input → output | When it fits | Limits & source |
|---|---|---|---|
| Tenderly EVM | Input: Transaction or bundle with selected network/state and optional overrides Output: Simulation traces, state changes and estimates | You need controlled previews and an inspectable execution context. | Results depend on the chosen block, transaction inputs and simulation environment. Documentation reviewed. Official source |
| Phalcon Explorer EVM | Input: An EVM transaction to investigate Output: Decoded calls, execution flow and asset movements | You need to reconstruct what an observed transaction did and inspect the trace. | Decoded labels and traces need interpretation against the underlying transaction and contract state. Documentation reviewed. Official source |
| Sentio EVM | Input: Configured protocol data and transaction/debugging context Output: Indexed observations and debugging views | You want to connect execution investigation with application-specific indexed data. | An indexer's coverage and processor logic determine which events reach the analysis. Documentation reviewed. Official source |
For a token-checking example, distinguish negative and unknown scanner results.
Public artifact walkthrough
Review Tenderly's distinction between simulation inputs and chain observations
The documentation separates simulation, virtual environments and debugging. Its simulation interface supports state overrides, which makes a scenario useful for investigation but changes what the result establishes. A review packet should state whether a balance or code value was changed and why. Preserve an untouched reference scenario when you need to explain the difference.
- Create a context record for the proposed transaction: chain, block, sender, recipient, calldata, value and any overrides.
- Compare the expected asset movements with the trace and post-state. Investigate unexpected approvals or privileged calls even if execution succeeds.
- Recheck immediately before an authorized production action when relevant state can change. This walkthrough does not authorize sending a transaction.