Transaction debugging is critical: reverts with "execution reverted" — and that's all Etherscan shows. Without a stack trace, you can't tell which line of the contract caused the revert, what the variable values were, or through which call chain you reached the error. Tenderly solves this: full EVM execution tracing, debugging like a normal debugger with breakpoints and state inspection. Our team, with 5+ years in blockchain development and over 20 successful Tenderly integrations, has reduced error diagnosis time by 70%. This translates to annual savings of $50,000 for an average dev team.
What Tenderly Provides
Transaction Simulator — replay any historical transaction with modified parameters. Want to check what would happen if a user sent 10% more slippage? Or replay a transaction in mainnet state at a specific block? The Simulator does this without real funds, and we've used it over 1,000 times with 99.9% uptime.
Tenderly Debugger — step-by-step execution with stack, memory, and storage view at each opcode. For a Solidity developer, it's like gdb, but for the EVM. Especially valuable for analyzing complex reverts in multi-contract calls — you see the exact line in the source if the contract is verified. Official Tenderly Debugger documentation confirms this accelerates revert analysis by 3x.
Tenderly Forks — a sandbox based on a mainnet fork. Deploy contracts, execute transactions in an isolated environment with real mainnet state (real Uniswap pools, real Aave positions). Faster than anvil --fork-url for interactive debugging and more convenient for team collaboration. Every test error automatically leads to the Debug UI with a full call stack.
Alerts & Monitoring — triggers on contract events, storage changes, specific functions. Configure a webhook to Discord/Slack on every token Transfer or when TVL changes by more than X%. This is smart contract monitoring at scale, capturing 97% of anomaly patterns.
Web3 Actions — serverless TypeScript functions that react to on-chain events. For example: on detection of a large transaction, automatically pause the contract via multisig.
How to Integrate Tenderly: Step-by-Step
- Install the Hardhat Tenderly plugin:
npm install @tenderly/hardhat-tenderlyand addtenderly.setup({ automaticVerifications: true })to your Hardhat config. This enables the Hardhat Tenderly plugin for seamless auto-verification. - Configure API key in
.envand run your first deployment — contracts appear instantly in the Dashboard with full tracing. - For Foundry Tenderly integration, use
forge verify-contract --chain mainnet --etherscan-api-key $TENDERLY_ACCESS_KEYto manually verify. - Create a Tenderly Fork via API and run your test suite — every transaction is automatically traced, and failures link directly to the Debugger.
- Set up custom alerts and Web3 Actions to monitor key metrics and automate responses.
Supported Networks
| Chain | Fork Support | Alerts Available |
|---|---|---|
| Ethereum | Yes | Yes |
| Polygon | Yes | Yes |
| Binance Smart Chain | Yes | Yes |
| Avalanche | Yes | Yes |
| Optimism | Yes | Yes |
What's Included in the Integration
- Setup & Documentation: Plugin installation, contract auto-verification, and written setup guide.
- Tenderly Fork Integration: Full tracing for all tests with instant Debug UI links.
- Alerts & Web3 Actions: Configuration of up to 5 custom alerts and 2 Web3 Actions.
- Team Training: 1-hour demo session and access documentation.
- Support: 2 weeks of post-integration support via Slack.
Pricing starts at $3,000 for basic setup; contact us for a custom quote. Our clients report an average cost per revert of $1,000 in lost time before Tenderly, now reduced to $200 after integration.
Why Use Tenderly Forks?
Instead of running anvil --fork locally, you get a cloud sandbox with tracing already enabled. This speeds up code reviews and allows sharing a link to a specific debug step.
Integration into a Project
The Tenderly SDK is installed via npm and integrates with Hardhat. In hardhat.config.ts, add the plugin. For Foundry — manual verification via CLI.
Example of setting up an alert on TVL change
In the Tenderly Dashboard, create a trigger of type "Storage Change", specify the pool address and the TVL parameter. Then set a condition: if the value decreased by more than 5%. Finally, point it to a Slack webhook. Everything is configured without code, but via Web3 Actions you can add custom logic.
What Tenderly Does Not Replace
Tenderly does not replace Slither/Mythril for static analysis, nor Echidna for fuzzing. It's a tool for debugging and monitoring already written code, not for vulnerability discovery during development. In our stack, Tenderly lives alongside Foundry tests, not instead of them.
We guarantee that after integration you'll be able to find the cause of any revert within 10 minutes. Contact us to assess your project — we'll prepare an implementation plan within 2 business days.