Tenderly Documentation
website·Indexed 37 days ago
https://docs.tenderly.coA platform for simulating, debugging, and monitoring onchain operations. Features include a smart contract debugger with gas profiling and expression evaluation, contract verification via Dashboard, Hardhat, and Foundry, a Developer Explorer for inspecting transactions and wallets, and an Alerts API for real-time on-chain event notifications.
What's inside Tenderly
- Account-scoped Alert destinations are notification targets that are accessible and usable across all projects within a single Tenderly account. These destinations allow you to route alerts to various third-party platforms from a centralized account configuration.
Overview of Multichain Virtual Environments
A Multichain Virtual Environment is a single testing resource that contains multiple blockchain networks (e.g., Ethereum, Arbitrum, Optimism, Base). It provides a shared identity across these networks, a unified cross-chain transaction timeline, and the ability to create, fund, and tear down all attached networks as a single unit. When combined with the Bridge Module, it can detect and relay cross-chain messages between networks within the same environment.Overview of Tenderly Alerts API
The Tenderly Alerts API allows for the creation of simple and complex alerting rules. A simple alert consists of a single rule (e.g., amethod_call), while a complex alert combines multiple conditions in an expressions array; the alert triggers only when all specified conditions are met. To define an alert, you must specify the delivery channels to be notified and the array of expressions that trigger the alert.Overview of State Sync for Virtual Environments
State Sync keeps a Virtual Environment in real-time synchronization with the state of its parent network. This allows developers to read live oracle prices, pool data, and account balances from the original chain while performing tests in a virtual environment. State Sync is available on paid plans.
Key characteristics:
- Activation: Enabled during the creation of a Virtual Environment by selecting the State only sync network sync mode.
- Immutability: The network sync mode is fixed at creation and cannot be changed later via the dashboard or API.
- Scope: Only state (storage, balances, nonces, and contract code) is synced. Parent-network transactions, event logs, and blocks do not appear in the Virtual Environment.
Overview of Tenderly Alert Destinations
Alert Destinations are the endpoints (such as email, Slack, webhooks, or Web3 Actions) that receive notifications when an on-chain alert is triggered in Tenderly. A single Destination can be linked to multiple Alerts, and a single Alert can be configured to send data to multiple Destinations.Overview of Tenderly Transaction Simulations
Tenderly allows developers to predict the exact outcome of single or bundled transactions before execution on the network. Simulations run in a virtual environment that replicates the real blockchain across 98 supported networks, providing 100% accurate gas usage breakdowns, asset exchanges, balance changes, storage updates, and decoded transaction traces.Overview of Tenderly MCP Server for AI Assistants
The Tenderly MCP Server implements the Model Context Protocol (MCP), an open standard by Anthropic that enables AI models to connect to external tools and data sources. This allows AI assistants to perform smart contract development tasks—such as creating Virtual Environments, simulating transactions, tracing execution, and inspecting contracts—directly within a conversation using natural language, eliminating the need for manual RPC responses or curl commands.Overview of Tenderly Web3 Actions
Tenderly Web3 Actions allow developers to run custom Node.js code in response to on-chain or off-chain events initiated by a smart contract. This enables the creation of a serverless backend that can monitor contract state changes, perform external API calls, or log data whenever specific conditions (like a smart contract event) are met.Overview of Tenderly Developer Explorer tools
Tenderly Developer Explorer is a suite of Web3 development tools used to inspect and debug transactions from any contract or wallet across all Tenderly-supported networks. The suite includes the following tools:
- Transaction Listing: A unified list of all transactions associated with your tracked contracts and wallets.
- Inspect Transaction: Detailed analysis of transaction call traces, state changes, and events.
- Debugger: A visual tool for identifying and fixing smart contract issues.
- Gas Profiler: A visual flame chart to examine contract gas usage by function and opcode.
- Simulator UI: A tool to test transaction outcomes by adjusting parameters and simulating results.
- Alerts: Real-time notifications for events occurring on tracked contracts or wallets.
Overview of Tenderly Platform Capabilities
Tenderly is a blockchain operations platform supporting 100+ networks. It provides a simulation-powered layer for engineering, finance, and risk teams to model transactions, deployments, and integrations against live network state before committing capital. The platform is divided into four primary functional areas: Simulator (pre-execution modeling), Console (post-execution analysis and debugging), Monitor (event detection and response), and Node RPC (high-performance infrastructure).Overview of Tenderly Virtual Environments
Virtual Environments are private blockchain environments that fork a live network (supporting 100+ EVM networks) to create a production-like testnet. They provide the realism of a production chain—including live oracle prices, liquidity pools, and governance state—without the cost or risk of using mainnet. They are primarily used as local node replacements, CI/CD infrastructure (provisioning environments per pull request), and staging/demo environments for QA and audits.Overview of Tenderly Simulator UI
The Tenderly Simulator allows developers to run transactions against live mainnet or testnet state without broadcasting them. It supports simulating as any sender, overriding contract storage, funding addresses, and manipulating block context. Users can perform 'single simulations' (one-step) or 'simulation bundles' (up to five sequential steps that share state changes).