# Table of Contents

- [Tenderly MCP Server examples with Claude - Tenderly](#tenderly-mcp-server-examples-with-claude-tenderly)
- [Tenderly MCP Server for Claude and AI assistants - Tenderly](#tenderly-mcp-server-for-claude-and-ai-assistants-tenderly)
- [Tenderly MCP Server tools reference - Tenderly](#tenderly-mcp-server-tools-reference-tenderly)
- [Tenderly MCP Server quickstart for Claude clients - Tenderly](#tenderly-mcp-server-quickstart-for-claude-clients-tenderly)
- [Unknown](#unknown)
- [Changelog - Tenderly](#changelog-tenderly)
- [Changelog - Tenderly](#changelog-tenderly)
- [Uniswap V3 - Tenderly](#uniswap-v3-tenderly)
- [Aave V3 - Tenderly](#aave-v3-tenderly)
- [Morpho - Tenderly](#morpho-tenderly)
- [Verify Contracts via Dashboard - Tenderly](#verify-contracts-via-dashboard-tenderly)
- [Gas Profiler - Tenderly](#gas-profiler-tenderly)
- [Transaction Listing - Tenderly](#transaction-listing-tenderly)
- [DeFi Modules - Tenderly](#defi-modules-tenderly)
- [War Room Aid Kit - Tenderly](#war-room-aid-kit-tenderly)
- [Evaluate Expressions with Advanced Debugger - Tenderly](#evaluate-expressions-with-advanced-debugger-tenderly)
- [Commenting & Prioritizing Traces - Tenderly](#commenting-prioritizing-traces-tenderly)
- [Smart Contract Verification - Tenderly](#smart-contract-verification-tenderly)
- [Fund Flow - Tenderly](#fund-flow-tenderly)
- [Claude और AI assistants के लिए Tenderly MCP Server - Tenderly](#claude-ai-assistants-tenderly-mcp-server-tenderly)
- [How to Use Tenderly Debugger - Tenderly](#how-to-use-tenderly-debugger-tenderly)
- [Investigating a Failed Transaction - Tenderly](#investigating-a-failed-transaction-tenderly)
- [Simulation Mode in the Explorer - Tenderly](#simulation-mode-in-the-explorer-tenderly)
- [Developer Explorer - Tenderly](#developer-explorer-tenderly)

---

# Tenderly MCP Server examples with Claude - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/ai-tools/examples#content-area)

These walkthroughs show how Claude uses [Tenderly MCP Server](https://docs.tenderly.co/ai-tools/overview)
 tools to complete real development tasks. If you haven’t connected it yet, follow the [MCP Server quickstart](https://docs.tenderly.co/ai-tools/quickstart)
 first. You don’t need to call tools by name, just describe what you want and Claude handles the rest. The examples are grouped roughly by activity:

*   **Setup & pre-flight**: spinning up environments, funding wallets, checking transactions before you sign.
*   **Debugging & post-mortem**: figuring out why a transaction failed, who took funds, or why a swap returned less than expected. The advanced trace navigation tools shine here.
*   **Virtual Environment workflows**: impersonation, multi-step testing, snapshots, time-travel, token balance overrides.
*   **Optimization & inspection**: gas breakdowns, contract metadata.

[​](https://docs.tenderly.co/ai-tools/examples#create-a-virtual-environment-and-fund-a-wallet)

Create a Virtual Environment and fund a wallet
------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Create a Virtual Environment forked from Ethereum mainnet and fund my wallet 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 with 100 ETH.”

**What Claude does:**

1.  Calls `list_projects` to find your projects, then `set_active_project` to select one.
2.  Calls `get_networks` to find the Ethereum mainnet network ID.
3.  Calls `create_vnet` with the network ID, creating a forked environment. The new Virtual Environment is automatically set as active.
4.  Calls `fund_account` with your wallet address, setting the balance to 100 ETH in hex wei. Operates on the active Virtual Environment automatically.
5.  Returns the Virtual Environment details including **Admin RPC** and **Public RPC** URLs, ready for use in Hardhat, Foundry, or any Web3 library.

**What you get back:** A running Virtual Environment forked from latest mainnet state, your wallet funded, and RPC URLs you can drop into your development framework config.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#simulate-a-uniswap-swap)

Simulate a Uniswap swap
--------------------------------------------------------------------------------------------------

**What to ask:**

> “Simulate a swap of 1 ETH for USDC on Uniswap V3 from 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 on Ethereum mainnet. Show me the expected output and any token transfers.”

**What Claude does:**

1.  Calls `simulate_transaction` with the Uniswap V3 router address, your sender address, the swap calldata, and 1 ETH as value.
2.  The simulation runs against current mainnet state and returns: success/revert status, gas used, and decoded method name.
3.  Calls `get_simulation_asset_transfers` to show all token movements, the ETH going in and USDC coming out.
4.  Calls `get_simulation_balance_changes` to show the net impact on your balances with USD values.

**What you get back:** The exact USDC output, gas cost, and a breakdown of every asset transfer. If the swap would revert (e.g., slippage too high), you get the decoded revert reason.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#pre-flight-check-a-transaction-before-sending)

Pre-flight check a transaction before sending
----------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “I’m about to call `approve` on 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 to give 0xE592427A0AEce92De3Edee1F18E0157C05861564 unlimited USDC allowance. Simulate it first and show me exactly what approvals and state changes it will create.”

**What Claude does:**

1.  Calls `simulate_transaction` with your wallet as sender, the token contract as recipient, and the `approve` calldata.
2.  Calls `get_simulation_exposure_changes` to show every approval and allowance change, which spender gets access to what, and how much.
3.  Calls `get_simulation_state_changes` to show the exact storage slots modified.

**What you get back:** The exact approval being granted (spender address, token, amount), the storage diff confirming the allowance slot changed, and whether the transaction would succeed. Useful any time you’re interacting with an unfamiliar contract or want to verify calldata before signing.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#debug-a-failed-on-chain-transaction)

Debug a failed on-chain transaction
--------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Why did transaction 0x6c5df5a1e6b34e2432ae19706e38a84239495cdbf40c2a9d4d79806443c4aa0d revert on Ethereum?”

**What Claude does:**

1.  Calls `trace_transaction` with the tx hash. Returns the status (`false` = reverted), gas used, decoded method name, and error message.
2.  Calls `get_simulation_call_trace` to get the full internal call tree, every function call, with decoded names, inputs, outputs, and which specific call failed.
3.  Calls `get_simulation_events` to see what events were emitted before the revert point.
4.  Optionally calls `get_simulation_state_changes` to see what state was modified up to the failure.

**What you get back:** A clear explanation of exactly which internal call failed, the decoded revert reason (e.g., `"ERC20: transfer amount exceeds balance"`), and the full call trace so you can see the execution path leading up to the failure.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#find-the-root-cause-of-a-revert-in-a-deeply-nested-transaction)

Find the root cause of a revert in a deeply nested transaction
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Transaction 0x… reverted on Ethereum. It’s a complex DeFi call with lots of internal calls, find the actual error and show me the path that led to it.”

**What Claude does:**

1.  Calls `trace_transaction` for the top-level summary and confirms the revert.
2.  Calls `find_failures` to list every failing call in the transaction, not just the outermost one. This surfaces both the originating revert and any wrapping `require`/try-catch failures.
3.  Calls `get_error_path` to return the blame chain from the root call down to the deepest failing call, with decoded inputs and outputs at each level.
4.  If any node still has omitted children, calls `get_call_trace_node` on the specific position to expand it.

**What you get back:** The exact contract, function, and decoded revert reason at the deepest failure, plus the full chain of callers that led there. Much faster than paging through a 200-call `get_simulation_call_trace` output.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#navigate-a-very-large-trace)

Navigate a very large trace
----------------------------------------------------------------------------------------------------------

**What to ask:**

> “This transaction has hundreds of internal calls and `get_simulation_call_trace` is truncated. Help me understand its structure and drill into the part that matters.”

**What Claude does:**

1.  Calls `get_trace_stats` to report total calls, max depth, error count, and unique contracts, a quick size check that decides the strategy.
2.  Calls `get_trace_skeleton` to get a compressed call tree: function name, contract, depth, and error flag per node, without decoded args.
3.  Identifies the interesting subtree (a failing branch, a specific protocol, or a suspicious contract) using `absolute_position` values from the skeleton.
4.  Calls `get_call_trace_node` to expand that subtree with full decoded inputs and outputs.
5.  Optionally calls `get_subtree_events` and `get_subtree_state_changes` to see only the events and storage diffs from that subtree.

**What you get back:** A map of the transaction’s structure, then full detail on just the part you care about, without loading thousands of calls into context.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#search-a-trace-for-a-specific-contract-or-function)

Search a trace for a specific contract or function
--------------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Did this transaction ever call `transferFrom` on USDC? If so, show me every call with the decoded args.”

**What Claude does:**

1.  Calls `search_call_trace` with the USDC address and `transferFrom` as filters, returning only matching calls with their decoded inputs, outputs, and absolute positions.
2.  For any match that’s interesting, calls `get_call_trace_node` to fetch the full nested context around it.

**What you get back:** A targeted list of matching calls instead of the full trace. Useful for answering “did X happen” questions on large transactions, and for auditing whether a known-risky selector was invoked.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#follow-the-money-through-a-transaction)

Follow the money through a transaction
--------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “For transaction 0x… on Ethereum, show me who sent what to whom, in order, with USD values.”

**What Claude does:**

1.  Calls `get_transaction_fund_flow` with the tx hash. Returns ordered token and native transfers, each with from/to addresses and USD values, plus a net flow per address.
2.  Optionally calls `get_contract_info` on any unfamiliar address to identify it (protocol router, pool, treasury, etc.).

**What you get back:** A chronological money map of the transaction and a per-address net flow, ideal for understanding MEV bundles, unfamiliar DeFi interactions, or verifying that a multi-hop swap moved funds as expected. On-chain transactions only.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#debug-a-failed-safe-multisig-batch-execution)

Debug a failed Safe multisig batch execution
--------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Our Safe batch execution at 0x… reverted on Ethereum. The batch has 12 calls. Which one actually failed and why?”

**What Claude does:**

1.  Calls `trace_transaction` to confirm the revert and get the top-level method (`execTransaction` or `multiSend`).
2.  Calls `get_trace_stats`, Safe batches explode into large traces quickly, so the stats decide the next step.
3.  Calls `find_failures`, because `multiSend` often reverts the whole batch on any sub-call failure, this is the fastest way to see which of the 12 operations blew up, not just the outer Safe revert.
4.  Calls `get_error_path` on the failing sub-call for the full decoded input/output chain at each level.
5.  Optionally calls `get_call_trace_node` if any relevant node was truncated.

**What you get back:** The exact sub-call inside the batch that failed, with the decoded target, function, arguments, and revert reason, rather than a generic “GS013” Safe error with no context.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#post-mortem-an-exploit-or-suspicious-transaction)

Post-mortem an exploit or suspicious transaction
----------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “0x… on Ethereum drained funds from our protocol. Walk me through what happened: who ended up with the money, what the attacker called, and where the exploit entered our contracts.”

**What Claude does:**

1.  Calls `get_transaction_fund_flow` first, the ordered token and native flows plus per-address net flow surface the attacker’s wallet and the drained protocol addresses immediately.
2.  Calls `get_trace_skeleton` to map the attacker’s call structure without loading every argument.
3.  Calls `search_call_trace` for calls into the protocol’s contracts (by address) to isolate the entry point.
4.  Calls `get_call_trace_node` on the entry point for decoded args, then `get_subtree_state_changes` to see exactly what state the exploit mutated.
5.  Calls `get_contract_info` on any unknown contracts the attacker interacted with (helpers, proxies, known exploit contracts).

**What you get back:** A money-first narrative of the exploit: who received what, the exact function and arguments that triggered the drain, and the state changes that made it possible. Enough detail to write an incident report or start a patch.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#investigate-an-unexpected-liquidation)

Investigate an unexpected liquidation
------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “My Aave position got liquidated in 0x…, figure out why. I want to know the oracle price at liquidation time and the exact health-factor path.”

**What Claude does:**

1.  Calls `trace_transaction` and `get_trace_skeleton` to map the liquidation call tree.
2.  Calls `search_call_trace` for oracle calls (e.g., `latestAnswer`, `getAssetPrice`) to find the price reads the liquidation used.
3.  Calls `get_call_trace_node` on each match for the decoded return values, the exact price feeding the health-factor math.
4.  Calls `get_transaction_fund_flow` to show how much collateral was seized, the debt repaid, and the liquidator’s bonus.
5.  Optionally calls `get_subtree_events` on the liquidation subtree for `LiquidationCall` and `Transfer` events in order.

**What you get back:** The oracle prices used, the liquidator’s profit, the exact collateral and debt amounts, and, if applicable, the block or transaction that moved your health factor below 1. A complete “why did I get liquidated” answer.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#audit-a-1inch-/-aggregator-swap-that-returned-less-than-expected)

Audit a 1inch / aggregator swap that returned less than expected
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “0x… was a 1inch swap where I got significantly less USDC than the quote. Which pool or hop gave the bad price?”

**What Claude does:**

1.  Calls `get_trace_stats`, aggregator routes can be deep with many pool hops.
2.  Calls `get_trace_skeleton` to see the sequence of pool calls in order.
3.  Calls `search_call_trace` for `swap`, `exactInput`, or the router’s pool-interaction selectors, pulling out each hop.
4.  Calls `get_call_trace_node` on each hop for decoded `amountIn` / `amountOut` values.
5.  Calls `get_transaction_fund_flow` to confirm the final net received and any unexpected transfers (fees, rebates).

**What you get back:** A per-hop breakdown of input and output amounts across the route, with the pool that had worse-than-expected execution called out. Useful for measuring slippage, comparing routes, or catching stale-quote issues.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#re-simulate-a-failed-transaction-with-a-fix)

Re-simulate a failed transaction with a fix
------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Transaction 0x… failed with ‘ERC20: transfer amount exceeds balance’. Re-simulate it but override my USDC balance to 10,000 USDC to confirm that’s the only issue.”

**What Claude does:**

1.  Calls `resimulate_transaction` with the original tx hash and a state override setting your token balance to 10,000 USDC.
2.  If the simulation succeeds, confirms the root cause was insufficient balance.
3.  Calls `get_simulation_call_trace` to verify the execution path now completes without error.
4.  Optionally calls `get_simulation_asset_transfers` to show what the transaction would have done if it had succeeded.

**What you get back:** Confirmation of whether the fix resolves the issue, without deploying anything or spending gas. State overrides let you test assumptions, insufficient balance, wrong allowance, incorrect ownership, instantly, against real mainnet state.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#understand-what-a-transaction-did)

Understand what a transaction did
----------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Walk me through everything that happened in transaction 0x… on Ethereum, every internal call, who called who, and what changed.”

**What Claude does:**

1.  Calls `trace_transaction` for a top-level summary: method name, sender, recipient, gas used, and status.
2.  Calls `get_simulation_call_trace` to get the full internal call tree, every nested call with decoded function names, inputs, outputs, and per-call gas.
3.  Calls `get_simulation_events` to list all events emitted in order.
4.  Calls `get_simulation_state_changes` to show every storage slot and balance that changed.

**What you get back:** A complete, human-readable reconstruction of the transaction. Useful for auditing unfamiliar protocol interactions, understanding MEV activity, or verifying that a complex multi-contract call did exactly what you expected.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#inspect-a-smart-contract)

Inspect a smart contract
----------------------------------------------------------------------------------------------------

**What to ask:**

> “What contract is deployed at 0xdAC17F958D2ee523a2206206994597C13D831ec7 on Ethereum?”

**What Claude does:**

1.  Calls `get_contract_info` with the address and Ethereum’s network ID.

**What you get back:** The contract name (Tether USD), token standards (ERC-20), compiler version, EVM version, source language, creation block, deployer address, creation transaction hash, and the full ABI. Claude can then use the ABI to help you encode calldata for simulations or build transactions.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#send-an-impersonated-transaction-on-a-virtual-environment-and-trace-it)

Send an impersonated transaction on a Virtual Environment and trace it
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “On my Virtual Environment, send a transaction from the Uniswap V2 deployer 0x1a9C8182C09F50C8318d769245beA52c32BE35BC to the USDC contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 calling the `transfer` function to send 1000 USDC to my wallet. Then trace the execution.”

**What Claude does:**

1.  Calls `send_vnet_transaction` on the active Virtual Environment with the deployer as `from`, USDC as `to`, and the ABI-encoded `transfer` calldata. The sender is impersonated, no private key needed.
2.  Calls `get_vnet_transactions` to get the `operation_id` of the executed transaction.
3.  Calls `trace_vnet_transaction` to get the decoded execution summary, contract name, function name, decoded input parameters, and output.
4.  Optionally calls `get_vnet_simulation_events` and `get_vnet_simulation_state_changes` for deeper details.

**What you get back:** Confirmation that the transaction executed, the decoded trace showing the `transfer` call succeeded, and the events emitted (Transfer event with your wallet as recipient).

* * *

[​](https://docs.tenderly.co/ai-tools/examples#test-a-multi-step-contract-interaction-on-a-virtual-environment)

Test a multi-step contract interaction on a Virtual Environment
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “On my Virtual Environment, run the full approval and swap flow: first approve the Uniswap router to spend 1000 USDC from my wallet, then execute the swap. Show me my balances before and after.”

**What Claude does:**

1.  Calls `send_vnet_transaction` on the active Virtual Environment to submit the `approve` transaction, impersonating your wallet, no private key needed.
2.  Calls `send_vnet_transaction` again with the swap calldata.
3.  Calls `get_vnet_simulation_asset_changes` on each transaction to show token movements per step.
4.  Calls `get_vnet_simulation_balance_changes` after the final step to show the net balance impact.

**What you get back:** Step-by-step confirmation that each transaction succeeded, token transfers per step, and your final net balance change. This is the full pre-deployment testing loop, run any sequence of transactions against a forked mainnet state before touching real funds.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#analyze-gas-usage-for-optimization)

Analyze gas usage for optimization
------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Simulate this transaction and show me a gas breakdown so I can find the most expensive function calls: \[paste calldata or describe the transaction\]”

**What Claude does:**

1.  Calls `simulate_transaction` with your transaction parameters.
2.  Calls `get_simulation_gas_breakdown` to get per-call gas consumption including intrinsic gas and refunds.
3.  Calls `get_simulation_call_trace` to map gas costs to specific function calls in the execution tree.

**What you get back:** A ranked list of the most gas-expensive operations, mapped to specific function calls. Use this to identify which parts of your contract logic to optimize.

Use `get_simulation_generated_access_list` to generate an EIP-2930 access list, which can reduce gas costs by pre-declaring which storage slots and addresses the transaction will access.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#fork-a-virtual-environment-for-parallel-testing)

Fork a Virtual Environment for parallel testing
--------------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “Fork my current Virtual Environment so I can test a different approach without losing the current state.”

**What Claude does:**

1.  Calls `list_vnets` to find your current Virtual Environment, then `set_active_vnet` if needed.
2.  Calls `fork_vnet`, creating a new Virtual Environment with all state preserved, deployed contracts, balances, and transaction history. The fork is automatically set as active.
3.  Returns the new Virtual Environment details with fresh RPC URLs.

**What you get back:** Two independent Virtual Environments sharing the same starting state. You can test different contract changes or transaction sequences in each without interference, like branching in git, but for blockchain state.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#snapshot-test-and-revert-for-stress-testing)

Snapshot, test, and revert for stress-testing
--------------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “On my Virtual Environment, snapshot the current state, then simulate a liquidation on Aave with different oracle prices. Revert to the snapshot between each attempt so I can compare outcomes.”

**What Claude does:**

1.  Calls `snapshot_vnet` to save the current Virtual Environment state, receiving a snapshot ID.
2.  Calls `set_storage_at` to override the oracle price to a specific value.
3.  Calls `send_vnet_transaction` to trigger the liquidation.
4.  Calls `get_vnet_simulation_balance_changes` and `get_vnet_simulation_asset_changes` to capture the outcome.
5.  Calls `revert_vnet` to restore the Virtual Environment to the snapshot state (the snapshot is consumed).
6.  Calls `snapshot_vnet` again for the next iteration, sets a different oracle price, and repeats.

**What you get back:** A side-by-side comparison of liquidation outcomes under different price scenarios, all tested against real forked state, without deploying anything or affecting other tests.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#set-erc-20-balances-for-testing)

Set ERC-20 balances for testing
------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “On my Virtual Environment, give my wallet 0xd8da6bf26964af9d7eed9e03e53415d37aa96045 a balance of 10,000 USDC and 5 WETH so I can test a swap.”

**What Claude does:**

1.  Calls `set_erc20_balance` with the USDC token address, your wallet, and the desired amount.
2.  Calls `set_erc20_balance` again with the WETH token address and amount.
3.  Optionally calls `vnet_call` with a `balanceOf` call to verify the balances were set correctly.

**What you get back:** Your wallet funded with exact token amounts, ready for testing. This is simpler than calculating storage slots manually, `set_erc20_balance` handles the token’s storage layout automatically.

* * *

[​](https://docs.tenderly.co/ai-tools/examples#time-travel-to-test-timelocks-and-vesting)

Time-travel to test timelocks and vesting
--------------------------------------------------------------------------------------------------------------------------------------

**What to ask:**

> “On my Virtual Environment, advance the clock by 7 days to test whether my timelock contract unlocks correctly.”

**What Claude does:**

1.  Calls `increase_time` with 604800 seconds (7 days) to advance the Virtual Environment clock.
2.  Calls `mine_block` to commit the time change to a new block.
3.  Calls `vnet_call` to read the timelock contract’s state (e.g., `isUnlocked()` or `releaseTime()`).
4.  Optionally calls `send_vnet_transaction` to execute the unlock and verify it succeeds.

**What you get back:** Confirmation of whether the timelock is unlockable after the time skip, without waiting 7 real days. Use this for any time-dependent logic: vesting schedules, governance voting periods, interest accrual, or cooldown windows.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Tenderly MCP Server for Claude and AI assistants - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/ai-tools/overview#content-area)

The Tenderly MCP Server gives AI assistants direct access to Tenderly, creating Virtual Environments, simulating transactions, tracing execution, inspecting contracts, and more. Use natural language in Claude to drive your entire smart contract development workflow.

The MCP Server is available on the paid plan. To enable it for your account, [contact our sales team](https://tenderly.co/contact-us)
. You also need a [Tenderly account](https://dashboard.tenderly.co/register)
 with at least one project.

[​](https://docs.tenderly.co/ai-tools/overview#get-started)

Get started
--------------------------------------------------------------------------

Quickstart
----------

Tools Reference
---------------

Examples
--------

[​](https://docs.tenderly.co/ai-tools/overview#what-is-mcp)

What is MCP?
---------------------------------------------------------------------------

The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/)
 is an open standard by Anthropic that lets AI models connect to external tools and data sources. Instead of copy-pasting RPC responses or writing curl commands, Claude can call Tenderly tools directly, live blockchain data, transaction simulation, debugging, and Virtual Environment management all happen within the conversation.

[​](https://docs.tenderly.co/ai-tools/overview#capabilities)

Capabilities
----------------------------------------------------------------------------

The MCP Server exposes **59 tools** across seven areas:

*   **Virtual Environments**: Create, fork, delete, and manage private blockchain environments. Set a Virtual Environment as active and all subsequent tools operate on it automatically. Fund accounts, set ERC-20 balances, write to storage slots, send impersonated transactions, make read-only contract calls, mine blocks, time-travel, and save/restore snapshots for branching test scenarios.
*   **Transaction Simulation**: Simulate any transaction on any supported EVM network without spending gas. Get decoded call traces, events, state changes, asset transfers, and balance diffs.
*   **Transaction Tracing**: Trace on-chain and Virtual Environment transactions with full execution details. Inspect call trees, gas breakdown, state diffs, and EIP-2930 access lists.
*   **Advanced Trace Navigation**: 16 tools for navigating complex transactions with hundreds or thousands of internal calls. Includes trace size inspection, skeleton views, subtree drilling, failure detection, error path tracing, and fund flow analysis.
*   **Contract Inspection**: Retrieve contract metadata for any address: name, ABI, compiler version, token standards, and creation info.
*   **Network Discovery**: List all 100+ EVM networks Tenderly supports.
*   **Project Management**: List projects and set the active project context.

See the full [Tools Reference](https://docs.tenderly.co/ai-tools/tools)
 for details on every tool.

[​](https://docs.tenderly.co/ai-tools/overview#supported-clients)

Supported clients
--------------------------------------------------------------------------------------

The Tenderly MCP Server works with any MCP-compatible client:

*   **Claude Code**: Add via CLI with one command
*   **Claude.ai**: Connect through Settings → Connectors
*   **Claude Desktop**: Connect through Settings → Connectors
*   **Cursor/VS Code**: Add the server URL to your MCP config

See the [Quickstart](https://docs.tenderly.co/ai-tools/quickstart)
 for setup instructions for each client.

[​](https://docs.tenderly.co/ai-tools/overview#authentication)

Authentication
--------------------------------------------------------------------------------

The MCP Server uses OAuth 2.0 via [WorkOS](https://workos.com/)
. When you connect from Claude, you’ll be redirected to Tenderly to log in and authorize access. Claude can only perform actions within the scope of your permissions. Revoke access at any time by disconnecting the connector in Claude.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Tenderly MCP Server tools reference - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/ai-tools/tools#content-area)

The [Tenderly MCP Server](https://docs.tenderly.co/ai-tools/overview)
 exposes 59 tools organized into seven groups. To connect it to your client first, follow the [MCP Server quickstart](https://docs.tenderly.co/ai-tools/quickstart)
. All tools that operate on project resources require an active project, call `set_active_project` first. Virtual Environment tools require an active Virtual Environment, call `set_active_vnet` or create/fork a Virtual Environment (which auto-activates it).

You don’t need to call tools by name. Just describe what you want in natural language and Claude will pick the right tools automatically.

[​](https://docs.tenderly.co/ai-tools/tools#project-&-account)

Project & account
-----------------------------------------------------------------------------------

These tools manage your session context. Most other tools depend on having an active project set.

| Tool | Description |
| --- | --- |
| `get_user_info` | Returns your account info (ID, username, email), the currently active project, and the active Virtual Environment (ID, RPC URL, network ID) if set. |
| `list_projects` | Lists all Tenderly projects accessible to you. Supports optional search filtering by name or slug. |
| `set_active_project` | Sets the active project for subsequent tool calls. Accepts `account_slug` and `project_slug`. Must be called before using project-scoped tools. |

[​](https://docs.tenderly.co/ai-tools/tools#networks)

Networks
-----------------------------------------------------------------

| Tool | Description |
| --- | --- |
| `get_networks` | Lists all public EVM networks supported by Tenderly (100+). Supports optional search filtering by name. Returns network ID, name, slug, and chain ID. |

[​](https://docs.tenderly.co/ai-tools/tools#contracts)

Contracts
-------------------------------------------------------------------

| Tool | Description |
| --- | --- |
| `get_contract_info` | Retrieves metadata for a contract address on a given network: contract name, ABI (if verified), compiler version, EVM version, language, token standards (ERC-20, ERC-721, etc.), creation block, creation transaction, and deployer address. |

[​](https://docs.tenderly.co/ai-tools/tools#transaction-simulations)

Transaction simulations
-----------------------------------------------------------------------------------------------

Simulate and trace transactions on any Tenderly-supported EVM network without spending gas or modifying on-chain state.

### 

[​](https://docs.tenderly.co/ai-tools/tools#core-simulation-tools)

Core simulation tools

| Tool | Description |
| --- | --- |
| `simulate_transaction` | Simulates a transaction and returns the outcome: success/revert status, gas used, decoded method name, error message, and revert reason. Supports state overrides, EIP-1559 fields, and custom block numbers. Results are persisted to your project dashboard. |
| `resimulate_transaction` | Replays an existing on-chain transaction in Tenderly’s simulation environment. Useful for debugging transactions that reverted or behaved unexpectedly. |
| `trace_transaction` | Traces an on-chain transaction and returns a summary: status, gas used, decoded method, sender, recipient, and error details. |

### 

[​](https://docs.tenderly.co/ai-tools/tools#simulation-detail-tools)

Simulation detail tools

After running `simulate_transaction`, `resimulate_transaction`, or `trace_transaction`, use these follow-up tools with the returned `simulation_id` or `tx_hash` to inspect specific aspects of the execution.

| Tool | Description |
| --- | --- |
| `get_simulation_call_trace` | Flattened call tree, every internal EVM call with decoded function names, inputs, outputs, and per-call gas. Supports `max_depth` parameter. Capped at 256 entries. |
| `get_simulation_events` | Decoded events (logs) emitted during execution, including event names, emitting addresses, and ABI-decoded parameters. Capped at 100 entries. |
| `get_simulation_state_changes` | Storage slot diffs (address, key, before/after values) and native balance diffs for all affected accounts. Capped at 100 entries. |
| `get_simulation_asset_transfers` | All token and native asset transfers: sender, recipient, token info (name, type, symbol, decimals), and amount. Capped at 100 entries. |
| `get_simulation_exposure_changes` | Token approval and allowance changes, approvals, revocations, and permits. Capped at 100 entries. |
| `get_simulation_balance_changes` | Net per-address balance impact with USD dollar values. Capped at 100 entries. |
| `get_simulation_gas_breakdown` | Per-call gas breakdown including intrinsic gas and refunds. Gas values are inclusive of subcalls. |
| `get_simulation_generated_access_list` | Generates an EIP-2930 access list by re-simulating the transaction. Useful for gas optimization. |

[​](https://docs.tenderly.co/ai-tools/tools#virtual-environments)

Virtual Environments
-----------------------------------------------------------------------------------------

Create and manage private, persistent forks of public EVM networks. Virtual Environments have their own RPC endpoints and support impersonated transactions without private keys. Virtual Environment tools use a **stateful session model**: set a Virtual Environment as active (or create/fork one, which auto-activates it), and all subsequent Virtual Environment tools operate on it. No need to pass Virtual Environment IDs to every call.

| Tool | Description |
| --- | --- |
| `set_active_vnet` | Sets the active Virtual Environment for subsequent tool calls. Accepts a `vnet_id`. Once set, all Virtual Environment tools operate on this Virtual Environment automatically. |
| `create_vnet` | Creates a new Virtual Environment by forking a public network at a specific block. Accepts `network_id`, optional `display_name`, `description`, `block_number` (hex), custom `chain_id`, and `sync_state_enabled`. Returns the Virtual Environment details including RPC URLs. **Automatically sets the new Virtual Environment as active.** |
| `list_vnets` | Lists Virtual Environments in the active project. Supports pagination (`page`, `per_page`), status filtering (`running`, `stopped`, `cloning`), and search by name. |
| `get_vnet` | Returns full details of the active Virtual Environment: ID, slug, display name, status, description, fork config, chain config, and RPC endpoint URLs. |
| `fork_vnet` | Forks the active Virtual Environment into a new one, preserving all state including deployed contracts and balances. **Automatically sets the new fork as active.** |
| `delete_vnet` | Deletes a Virtual Environment. This is a destructive action. Clears the active Virtual Environment from session state. |
| `send_vnet_transaction` | Sends and executes a transaction on the active Virtual Environment. The sender address is impersonated, no private key needed. Accepts `from`, `to`, `input` (calldata), `value` (hex wei), and `gas`. |
| `get_vnet_transactions` | Lists transactions on the active Virtual Environment with pagination. Returns transaction hash, status, gas used, block number, and method. |
| `fund_account` | Sets the native token balance of any address on the active Virtual Environment by calling `tenderly_setBalance` via RPC. Accepts `address` and `amount` in hex wei. |
| `set_erc20_balance` | Sets the ERC-20 token balance of any address on the active Virtual Environment via `tenderly_setErc20Balance`. Accepts `token_address`, `address`, and `value`. Prefer this over `set_storage_at` for token balance changes. |
| `set_storage_at` | Writes a raw value to a specific storage slot on a contract via `tenderly_setStorageAt`. Accepts `contract_address`, `slot`, and `value`. Use for oracle price overrides, protocol parameters, or any state not covered by higher-level tools. |
| `vnet_call` | Executes a read-only `eth_call` on the active Virtual Environment. Accepts `to`, `input` (calldata), and optional `from`. Results are truncated at 10 KB. |
| `vnet_multicall` | Executes a batch of up to 10 read-only `eth_call` requests in a single RPC round-trip. Each call accepts `to`, `input`, and optional `from`. Results are truncated individually at 10 KB. |
| `mine_block` | Mines a single block on the active Virtual Environment via `evm_mine`. Use after `increase_time` to apply the time change. |
| `increase_time` | Advances the Virtual Environment clock by a specified number of seconds via `evm_increaseTime`. Always follow with `mine_block` to commit the time change to a new block. |
| `snapshot_vnet` | Saves the current Virtual Environment state and returns a snapshot ID via `evm_snapshot`. Use for branching test scenarios, snapshot before a test, then revert to try a different path. |
| `revert_vnet` | Restores the Virtual Environment to a previously saved snapshot via `evm_revert`. The snapshot is consumed on use, take a new snapshot if you need to revert again. |

[​](https://docs.tenderly.co/ai-tools/tools#virtual-environment-simulations-&-traces)

Virtual Environment simulations & traces
---------------------------------------------------------------------------------------------------------------------------------

Simulate and trace transactions on the active Virtual Environment. These tools work with operation IDs rather than network-level tx hashes.

### 

[​](https://docs.tenderly.co/ai-tools/tools#core-virtual-environment-simulation-tools)

Core Virtual Environment simulation tools

| Tool | Description |
| --- | --- |
| `simulate_vnet_transaction` | Simulates a transaction on a Virtual Environment without modifying its state. Returns status, gas used, decoded method, and an `operation_id` for follow-up tools. Supports state overrides. |
| `resimulate_vnet_transaction` | Re-traces a previously executed Virtual Environment transaction by its `operation_id` (from `get_vnet_transactions`). |
| `trace_vnet_transaction` | Returns a decoded execution trace summary: contract name, function name, decoded input parameters, decoded output, gas used, and error details. |

### 

[​](https://docs.tenderly.co/ai-tools/tools#virtual-environment-simulation-detail-tools)

Virtual Environment simulation detail tools

Use these with the `operation_id` from the tools above. They operate on the active Virtual Environment.

| Tool | Description |
| --- | --- |
| `get_vnet_simulation_call_trace` | Flattened call trace for a Virtual Environment transaction with call type, addresses, gas, and value per call. |
| `get_vnet_simulation_events` | Decoded events emitted during a Virtual Environment transaction: event name and emitting address. |
| `get_vnet_simulation_gas_breakdown` | Per-call gas breakdown sorted by gas usage. Shows total gas and top consumers. |
| `get_vnet_simulation_state_changes` | Storage slot diffs: address, key, before/after values for each modified slot. |
| `get_vnet_simulation_generated_access_list` | EIP-2930 access list generated from the Virtual Environment transaction execution. |
| `get_vnet_simulation_balance_changes` | Net per-address balance changes with dollar values. |
| `get_vnet_simulation_asset_changes` | Token and native asset transfers: type, from, to, amount, and token info. |

[​](https://docs.tenderly.co/ai-tools/tools#advanced-trace-navigation)

Advanced trace navigation
---------------------------------------------------------------------------------------------------

16 tools for navigating complex transactions with hundreds or thousands of internal calls. Use these when `get_simulation_call_trace` or `get_vnet_simulation_call_trace` returns truncated results, or when you need to search, drill into, or summarize a large trace without loading the full tree.

### 

[​](https://docs.tenderly.co/ai-tools/tools#on-chain-&-simulation)

On-chain & simulation

| Tool | Description |
| --- | --- |
| `get_trace_stats` | Quick size check before loading a trace, returns total calls, max depth, error count, and unique contracts. Use to decide which navigation strategy to apply. |
| `get_trace_skeleton` | Returns a compressed call tree (function name, contract, depth, error flag, no decoded args) for large truncated traces. Use the returned `absolute_position` values to drill in. |
| `get_call_trace_node` | Expands a specific truncated node in the trace. Use when a node reports `omitted_children > 0`. |
| `search_call_trace` | Searches a large trace for specific calls without loading the full tree. Filter by address, function name, or error status. |
| `get_subtree_events` | Returns events from one specific subtree instead of the full transaction. Use when `get_simulation_events` returns too many events. |
| `get_subtree_state_changes` | Returns storage diffs from one specific subtree. |
| `find_failures` | Finds all error locations in a transaction at once, returns every failing node with contract name, function, and decoded error. |
| `get_error_path` | Shows the blame chain from root to the deepest error with decoded inputs/outputs at each level. The go-to tool for debugging reverts in complex transactions. |
| `get_transaction_fund_flow` | Shows ordered money movement in a transaction, who sent what to whom with USD values and net flow per address. On-chain transactions only. |

### 

[​](https://docs.tenderly.co/ai-tools/tools#virtual-environment-equivalents)

Virtual Environment equivalents

Mirror of the tools above for transactions on the active Virtual Environment.

| Tool | Description |
| --- | --- |
| `get_vnet_trace_stats` | Virtual Environment equivalent of `get_trace_stats`. |
| `get_vnet_trace_skeleton` | Virtual Environment equivalent of `get_trace_skeleton`. |
| `get_vnet_call_trace_node` | Virtual Environment equivalent of `get_call_trace_node`. |
| `search_vnet_call_trace` | Virtual Environment equivalent of `search_call_trace`. |
| `get_vnet_subtree_events` | Virtual Environment equivalent of `get_subtree_events`. |
| `find_vnet_failures` | Virtual Environment equivalent of `find_failures`. |
| `get_vnet_error_path` | Virtual Environment equivalent of `get_error_path`. |

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Tenderly MCP Server quickstart for Claude clients - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/ai-tools/quickstart#content-area)

Get the Tenderly MCP Server running in your AI assistant in under a minute.

The MCP Server is available on the paid plan. To enable it for your account, [contact our sales team](https://tenderly.co/contact-us)
.

[​](https://docs.tenderly.co/ai-tools/quickstart#prerequisites)

Prerequisites
--------------------------------------------------------------------------------

*   A [Tenderly account](https://dashboard.tenderly.co/register)
     with MCP Server access enabled
*   At least one Tenderly project

[​](https://docs.tenderly.co/ai-tools/quickstart#connect-to-the-mcp-server)

Connect to the MCP Server
--------------------------------------------------------------------------------------------------------

*   Shell
    
*   1\. Open \[claude.ai\](https://claude.ai) a
    
*   1\. Open Claude Desktop and go to Setting
    
*   JSON
    

Run the following command in your terminal:

    claude mcp add tenderly --transport http https://mcp.tenderly.co/mcp
    

Verify the server is connected:

    claude mcp list
    

Run `/mcp` inside Claude Code, select **tenderly**, and follow the browser login to authenticate.

1.  Open [claude.ai](https://claude.ai/)
     and go to **Settings → Connectors**.
2.  Click **Add custom connector** at the bottom.
3.  Enter the URL: `https://mcp.tenderly.co/mcp`
4.  Click **Add** and complete the OAuth login.

Once connected, Tenderly tools are available in any conversation.

> **Note:** Custom connectors require a Pro or higher Claude plan. On Enterprise plans, only workspace admins can add connectors.

1.  Open Claude Desktop and go to **Settings → Connectors**.
2.  Click **Add custom connector**.
3.  Enter the URL: `https://mcp.tenderly.co/mcp`
4.  Click **Add** and complete the OAuth login.

> **Note:** Custom connectors require a Pro or higher Claude plan. On Enterprise plans, only workspace admins can add connectors.

Add the following to your MCP configuration file (`.cursor/mcp.json`, `.vscode/mcp.json`, or equivalent):

    {
      "mcpServers": {
        "tenderly": {
          "type": "streamable-http",
          "url": "https://mcp.tenderly.co/mcp"
        }
      }
    }
    

Your editor will prompt you to authenticate when you first use a Tenderly tool.

[​](https://docs.tenderly.co/ai-tools/quickstart#first-tool-call)

First tool call
------------------------------------------------------------------------------------

Once connected, try a simple prompt to verify everything works:

> “What is my account name and currently active project?”

Claude will call `get_user_info` and returns your account information and the currently active project (if set). If this works, you’re all set.

[​](https://docs.tenderly.co/ai-tools/quickstart#set-your-active-project)

Set your active project
----------------------------------------------------------------------------------------------------

Most tools require a project context. Set it once per session:

> “Set my active project to my-project under my-account”

Claude will call `set_active_project`. All subsequent tool calls (simulations, Virtual Environments, traces) will use this project.

You can also let Claude figure out the project automatically, just ask it to do something and it will call `list_projects` first if needed.

[​](https://docs.tenderly.co/ai-tools/quickstart#troubleshooting)

Troubleshooting
------------------------------------------------------------------------------------

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#authentication-fails-or-the-connector-won%E2%80%99t-log-in)

Authentication fails or the connector won’t log in

If the OAuth login loops or errors out, disconnect the Tenderly connector in your Claude client (Settings → Connectors) and re-add it. In Claude Code, run `/mcp`, select **tenderly**, and redo the browser login. Custom connectors on Claude.ai and Claude Desktop require a Pro or higher plan, on Enterprise plans, only workspace admins can add them. If reconnecting doesn’t help and requests return HTTP 403, see the [plan restriction below](https://docs.tenderly.co/ai-tools/quickstart#http-403-your-current-plan-does-not-include-mcp-access)
.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#http-403-your-current-plan-does-not-include-mcp-access)

HTTP 403: Your current plan does not include MCP access

This is a plan restriction, not an authentication problem. The MCP Server is available on the paid plan; on accounts without MCP access, every request returns HTTP 403 with the `quota_limit_reached` error even after a successful OAuth login. Some MCP clients react to the `insufficient_scope` response by restarting the OAuth flow, so the restriction can surface as a login loop. Re-authenticating does not resolve it. To enable MCP Server access for your account, [contact our sales team](https://tenderly.co/contact-us)
.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#%E2%80%9Dno-active-project%E2%80%9D-errors)

”No active project” errors

Most tools require a project context. Ask Claude to set one:

> “Set my active project to my-project under my-account”

Or let Claude pick automatically by asking it to list projects first.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#%E2%80%9Dno-active-virtual-environment%E2%80%9D-errors)

”No active Virtual Environment” errors

Virtual Environment tools operate on the active Virtual Environment. Either create/fork a Virtual Environment (which auto-activates it) or ask Claude to call `set_active_vnet` with an existing Virtual Environment ID.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#call-trace-or-events-are-truncated)

Call trace or events are truncated

`get_simulation_call_trace` is capped at 256 entries and `get_simulation_events` at 100. For large transactions, use the [Advanced Trace Navigation](https://docs.tenderly.co/ai-tools/tools#advanced-trace-navigation)
 tools: start with `get_trace_stats` for size, then `get_trace_skeleton` to see the tree structure, and `get_call_trace_node`, `get_subtree_events`, or `search_call_trace` to drill into specific parts. For reverts, `find_failures` and `get_error_path` are usually the fastest path to the root cause.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#claude-picks-the-wrong-network-project-or-virtual-environment)

Claude picks the wrong network, project, or Virtual Environment

Be explicit in the prompt, name the network, project slug, or Virtual Environment. You can also ask Claude to confirm the active context with `get_user_info` before running a task.

### 

[​](https://docs.tenderly.co/ai-tools/quickstart#a-tool-call-returns-stale-or-wrong-data)

A tool call returns stale or wrong data

Active project and Virtual Environment state is per-session. If you switch projects or Virtual Environments mid-conversation, confirm the active context with `get_user_info` before running follow-up tools.

[​](https://docs.tenderly.co/ai-tools/quickstart#next-steps)

Next steps
--------------------------------------------------------------------------

*   [Tools Reference](https://docs.tenderly.co/ai-tools/tools)
    : See all 59 tools and what they do
*   [Examples](https://docs.tenderly.co/ai-tools/examples)
    : Walkthroughs for common workflows
*   [Virtual Environments](https://docs.tenderly.co/virtual-environments/overview)
    : Learn more about the environments you can create
*   [Simulations](https://docs.tenderly.co/simulations/overview)
    : Understand how transaction simulation works

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Unknown

\# Tenderly Documentation > Official Tenderly documentation for Virtual Environments, Node RPC, Web3 Actions, Debugger, Simulations, Alerts, Monitoring, and the full Tenderly developer platform. Tenderly is a Web3 development platform for building, testing, monitoring, and operating smart contracts across 80+ EVM networks. These docs cover product usage, SDKs, APIs, and JSON-RPC references. Canonical site: https://docs.tenderly.co API reference: https://docs.tenderly.co/reference/api Dashboard: https://dashboard.tenderly.co ## Overview - \[All products\](https://docs.tenderly.co/products): Explore all Tenderly products by category. - \[Supported Networks & Languages\](https://docs.tenderly.co/supported-networks): A list of all EVM-compatible networks supported in Tenderly - \[Tenderly Documentation\](https://docs.tenderly.co/): Learn all about the Tenderly platform and how it provides a fully integrated Web3 developer experience. - \[Tenderly TX Preview Snap\](https://docs.tenderly.co/how-to-install-tenderly-tx-preview-snap): Preview transactions before sending them on-chain to get valuable insights, avoid failed transactions, and save funds. - \[Tenderly Units (TU)\](https://docs.tenderly.co/pricing): Tenderly Units - the measure of computational resources consumption on the Tenderly full-stack node. ## Virtual Environments - \[Adding Virtual Environments to Wallets\](https://docs.tenderly.co/virtual-environments/interact/add-to-wallet): Send transactions to Virtual Environments securely through MetaMask. - \[Bytecode deployment cheatcode\](https://docs.tenderly.co/virtual-environments/develop/bytecode-deployment-cheat-code): Learn how you can deploy custom bytecode to any address using tenderly\_setCode Admin RPC method. - \[Connect Dapp UI to Virtual Environment\](https://docs.tenderly.co/virtual-environments/ci-cd/stage-dapps): Make it effortless connect and send transactions to staged dapps for manual and end-to-end testing by adding Virtual Environment to wallets using RainbowKit. - \[Connect to a WebSocket on Virtual Environments\](https://docs.tenderly.co/virtual-environments/interact/websockets): Real-time blockchain updates with Tenderly WebSockets - \[ConnectKit\](https://docs.tenderly.co/virtual-environments/dapp-ui/connectkit): Learn how to configure Virtual Environments with ConnectKit when building, staging, and demoing dapps. - \[Custom RPC Methods\](https://docs.tenderly.co/virtual-environments/admin-rpc): Explore the list of network customization RPC methods available in Virtual Environments. Use these methods to manipulate network state, balances, and history. - \[Debugging Transactions\](https://docs.tenderly.co/virtual-environments/develop/debug-transactions): Debugging Transactions - \[Deploy Contracts on Virtual Environments\](https://docs.tenderly.co/virtual-environments/develop/deploy-contracts): Deploy Contracts with Foundry and Hardhat - \[Dynamic\](https://docs.tenderly.co/virtual-environments/dapp-ui/dynamic): Learn how to configure Virtual Environments with Dynamic UI kit when building, staging, and demoing dapps. - \[Ethers.js\](https://docs.tenderly.co/virtual-environments/client-libraries/ethers): Learn how to use Ethers.js to connect to a blockchain network through Node RPC. - \[Fork a Virtual Environment\](https://docs.tenderly.co/virtual-environments/develop/fork-testnet): Fork a Virtual Environment - \[Foundry and Github Actions\](https://docs.tenderly.co/virtual-environments/ci-cd/github-actions-foundry): Set up a CI/CD pipeline on Virtual Environments with the Tenderly GitHub Action to test and stage Solidity smart contracts using Foundry. - \[Hardhat\](https://docs.tenderly.co/virtual-environments/smart-contract-frameworks/hardhat): Deploy Solidity contracts to a Virtual Environment using Hardhat. - \[Hardhat and Github Actions\](https://docs.tenderly.co/virtual-environments/ci-cd/github-actions-hardhat): Use Tenderly Github action to set up Continuous Integration and Continuous Deployment (CI/CD) to test and stage Solidity smart contracts with Hardhat - \[RainbowKit\](https://docs.tenderly.co/virtual-environments/dapp-ui/rainbowkit): Learn how to configure RainbowKit with Virtual Environments when building, staging, and demoing dapps. - \[Reown AppKit\](https://docs.tenderly.co/virtual-environments/dapp-ui/reown-app-kit): Learn how to connect ConnectKit to Virtual Environments when building, staging, and demoing dapps. - \[Revert State\](https://docs.tenderly.co/virtual-environments/develop/revert-state): Revert State - \[Sending Transactions to Virtual Environment\](https://docs.tenderly.co/virtual-environments/interact/send-transactions): Sending Transactions to Virtual Environment - \[Simulate Transactions\](https://docs.tenderly.co/virtual-environments/interact/simulate-transactions): Simulate Transactions - \[Staging Contracts\](https://docs.tenderly.co/virtual-environments/ci-cd/stage-contracts): Learn how to stage contracts within CI/CD using Virtual Environments - \[State Sync\](https://docs.tenderly.co/virtual-environments/state-sync): Understand how Tenderly Virtual Environments State Sync works. - \[The Graph and Virtual Environments\](https://docs.tenderly.co/virtual-environments/develop/thegraph): Guide to setting up and using Tenderly Virtual Environments alongside The Graph. - \[Thirdweb\](https://docs.tenderly.co/virtual-environments/dapp-ui/thirdweb): Using ThirdWeb SDK with Virtual Environments - \[Unlimited Faucet\](https://docs.tenderly.co/virtual-environments/unlimited-faucet): Use Unlimited Faucet to fund native and ERC-20 tokens to any account - \[Using Foundry\](https://docs.tenderly.co/virtual-environments/smart-contract-frameworks/foundry): Deploy Solidity contracts to a Virtual Environment using Foundry. - \[Viem\](https://docs.tenderly.co/virtual-environments/client-libraries/viem): Learn how to connect Viem to Virtual Environments - \[Virtual Environment Explorer\](https://docs.tenderly.co/virtual-environments/explorer): Virtual Environment Explorer - \[Virtual Environment Integration Guides\](https://docs.tenderly.co/virtual-environments/integrations): Learn how to integrate Virtual Environments with different client libraries, smart contract development frameworks, and UI libraries. - \[Virtual Environment Pricing\](https://docs.tenderly.co/virtual-environments/pricing): Learn more about Virtual Environment pricing. - \[Virtual Environments\](https://docs.tenderly.co/virtual-environments): Virtual Environments replace public testnets with live data sync, unlimited faucets, and a shareable block explorer for dev, CI/CD, and staging. - \[Virtual Environments Quickstart\](https://docs.tenderly.co/virtual-environments/quickstart): Learn how to quickly spin up a Virtual Environment and start interacting with it. - \[Virtual Environments REST API\](https://docs.tenderly.co/virtual-environments/develop/rest-api): Use REST API to create Virtual Environments and interact - \[Wagmi\](https://docs.tenderly.co/virtual-environments/dapp-ui/wagmi): Learn how to connect Wagmi with Virtual Environments when building, staging, and demoing dapps. - \[Working with timestamps on Virtual Environments\](https://docs.tenderly.co/virtual-environments/develop/working-with-timestamps): Learn how you can access the correct timestamp and advance time on Virtual Environments ## Node RPC - \[ApeChain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/apechain): Explore ApeChain JSON-RPC methods via Tenderly Node RPC. Connect to ApeChain (chain ID: 33139) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ApexFusion Nexus Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/af-nexus-mainnet): Explore ApexFusion Nexus Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to ApexFusion Nexus Mainnet (chain ID: 9069) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ApexFusion Nexus Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/af-nexus-testnet): Explore ApexFusion Nexus Testnet JSON-RPC methods via Tenderly Node RPC. Connect to ApexFusion Nexus Testnet (chain ID: 9070) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Arbitrum Nova Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/arbitrum-nova): Explore Arbitrum Nova JSON-RPC methods via Tenderly Node RPC. Connect to Arbitrum Nova (chain ID: 42170) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Arbitrum One Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/arbitrum): Explore Arbitrum One JSON-RPC methods via Tenderly Node RPC. Connect to Arbitrum One (chain ID: 42161) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Arbitrum Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/arbitrum-sepolia): Explore Arbitrum Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Arbitrum Sepolia (chain ID: 421614) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Avalanche C-Chain Fuji Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/avalanche-fuji): Explore Avalanche C-Chain Fuji JSON-RPC methods via Tenderly Node RPC. Connect to Avalanche C-Chain Fuji (chain ID: 43113) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Avalanche C-Chain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/avalanche): Explore Avalanche C-Chain JSON-RPC methods via Tenderly Node RPC. Connect to Avalanche C-Chain (chain ID: 43114) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Base Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/base-mainnet): Explore Base Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to Base Mainnet (chain ID: 8453) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Base Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/base-sepolia): Explore Base Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Base Sepolia (chain ID: 84532) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Batching JSON-RPC requests\](https://docs.tenderly.co/node/guides/request-batching): Batch several JSON-RPC method calls to reduce the impact of HTTP requests latency - \[Bepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/bepolia): Explore Bepolia JSON-RPC methods via Tenderly Node RPC. Connect to Bepolia (chain ID: 80069) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Berachain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/berachain): Explore Berachain JSON-RPC methods via Tenderly Node RPC. Connect to Berachain (chain ID: 80094) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Blast Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/blast): Explore Blast JSON-RPC methods via Tenderly Node RPC. Connect to Blast (chain ID: 81457) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[BOB Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/bob): Explore BOB JSON-RPC methods via Tenderly Node RPC. Connect to BOB (chain ID: 60808) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[BOB Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/bob-testnet): Explore BOB Testnet JSON-RPC methods via Tenderly Node RPC. Connect to BOB Testnet (chain ID: 808813) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Boba Ethereum Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/boba-ethereum-mainnet): Explore Boba Ethereum JSON-RPC methods via Tenderly Node RPC. Connect to Boba Ethereum (chain ID: 288) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Boba Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/boba-sepolia): Explore Boba Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Boba Sepolia (chain ID: 28882) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Celo Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/celo): Explore Celo Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to Celo Mainnet (chain ID: 42220) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Celo Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/celo-sepolia): Explore Celo Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Celo Sepolia (chain ID: 11142220) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Conflux eSpace Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/cfx-espace): Explore Conflux eSpace JSON-RPC methods via Tenderly Node RPC. Connect to Conflux eSpace (chain ID: 1030) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Conflux eSpace Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/cfx-espace-testnet): Explore Conflux eSpace Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Conflux eSpace Testnet (chain ID: 71) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ConnectKit - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/connect-kit): Learn how to configure your ConnectKit components to use Node RPC as an RPC provider. - \[Curtis Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/curtis): Explore Curtis JSON-RPC methods via Tenderly Node RPC. Connect to Curtis (chain ID: 33111) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Dynamic - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/dynamic): Learn how to set Node RPC as an RPC provider in Dynamic components. - \[Ethereum Hoodi Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/hoodi): Explore Ethereum Hoodi JSON-RPC methods via Tenderly Node RPC. Connect to Ethereum Hoodi (chain ID: 560048) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ethereum Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet): Explore Ethereum Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to Ethereum Mainnet (chain ID: 1) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ethereum Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ethereum-sepolia): Explore Ethereum Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Ethereum Sepolia (chain ID: 11155111) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ethers.js - Node RPC Integration\](https://docs.tenderly.co/node/integrations-chain-interaction/ethers): Learn how to use Ethers.js to connect to a blockchain network through Node RPC. - \[Flare Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/flare): Explore Flare JSON-RPC methods via Tenderly Node RPC. Connect to Flare (chain ID: 14) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Foundry - Node RPC Integration\](https://docs.tenderly.co/node/integrations-smart-contract-frameworks/foundry): Learn how to deploy contracts and run scripts from Foundry using Node RPC. - \[Fraxtal Hoodi Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/fraxtal-hoodi): Explore Fraxtal Hoodi JSON-RPC methods via Tenderly Node RPC. Connect to Fraxtal Hoodi (chain ID: 2523) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Fraxtal Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/fraxtal): Explore Fraxtal JSON-RPC methods via Tenderly Node RPC. Connect to Fraxtal (chain ID: 252) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Gnosis Chain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/gnosis-chain): Explore Gnosis Chain JSON-RPC methods via Tenderly Node RPC. Connect to Gnosis Chain (chain ID: 100) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Gnosis Chiado Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/gnosis-chiado-testnet): Explore Gnosis Chiado Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Gnosis Chiado Testnet (chain ID: 10200) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Go-Ethereum (geth) - Node RPC Integration\](https://docs.tenderly.co/node/integrations-chain-interaction/go): Learn how to connect to Node RPC from Go-Ethereum (geth). - \[Hardhat - Node RPC\](https://docs.tenderly.co/node/integrations-smart-contract-frameworks/hardhat): Learn how to deploy contracts through Node RPC from your Hardhat projects. - \[Immutable Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/immutable): Explore Immutable JSON-RPC methods via Tenderly Node RPC. Connect to Immutable (chain ID: 13371) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Immutable Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/immutable-testnet): Explore Immutable Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Immutable Testnet (chain ID: 13473) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ink Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ink): Explore Ink JSON-RPC methods via Tenderly Node RPC. Connect to Ink (chain ID: 57073) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ink Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ink-sepolia): Explore Ink Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Ink Sepolia (chain ID: 763373) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Integration Guides\](https://docs.tenderly.co/node/integrations): Learn how to integrate Node RPC with different client libraries, smart contract development frameworks, and UI libraries. - \[Katana Bokuto Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/katana-bokuto): Explore Katana Bokuto JSON-RPC methods via Tenderly Node RPC. Connect to Katana Bokuto (chain ID: 737373) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Katana Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/katana): Explore Katana JSON-RPC methods via Tenderly Node RPC. Connect to Katana (chain ID: 747474) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Lens Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/lens): Explore Lens JSON-RPC methods via Tenderly Node RPC. Connect to Lens (chain ID: 232) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Lens Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/lens-sepolia): Explore Lens Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Lens Testnet (chain ID: 37111) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Linea Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/linea): Explore Linea JSON-RPC methods via Tenderly Node RPC. Connect to Linea (chain ID: 59144) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Linea Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/linea-sepolia): Explore Linea Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Linea Sepolia (chain ID: 59141) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Lisk Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/lisk): Explore Lisk JSON-RPC methods via Tenderly Node RPC. Connect to Lisk (chain ID: 1135) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Lisk Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/lisk-sepolia): Explore Lisk Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Lisk Sepolia (chain ID: 4202) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Mantle Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/mantle): Explore Mantle JSON-RPC methods via Tenderly Node RPC. Connect to Mantle (chain ID: 5000) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Mantle Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/mantle-sepolia): Explore Mantle Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Mantle Sepolia (chain ID: 5003) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[MegaETH Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/megaeth): Explore MegaETH JSON-RPC methods via Tenderly Node RPC. Connect to MegaETH (chain ID: 4326) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Metis Andromeda Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/metis-andromeda): Explore Metis Andromeda JSON-RPC methods via Tenderly Node RPC. Connect to Metis Andromeda (chain ID: 1088) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Metis Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/metis-sepolia): Explore Metis Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Metis Sepolia (chain ID: 59902) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Monad Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/monad): Explore Monad JSON-RPC methods via Tenderly Node RPC. Connect to Monad (chain ID: 143) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Monad Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/monad-testnet): Explore Monad Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Monad Testnet (chain ID: 10143) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Moonbase Alpha Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/moonbase-alpha): Explore Moonbase Alpha JSON-RPC methods via Tenderly Node RPC. Connect to Moonbase Alpha (chain ID: 1287) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Moonbeam Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/moonbeam): Explore Moonbeam JSON-RPC methods via Tenderly Node RPC. Connect to Moonbeam (chain ID: 1284) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Moonriver Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/moonriver): Explore Moonriver JSON-RPC methods via Tenderly Node RPC. Connect to Moonriver (chain ID: 1285) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Node Extensions\](https://docs.tenderly.co/node/node-extensions): Build your own custom RPC methods and run them through Node RPC with Node Extensions. - \[Node RPC\](https://docs.tenderly.co/node): Deploy contracts, send and simulate transactions, and read blockchain data via RPC using Node RPC. - \[Node RPC Reference\](https://docs.tenderly.co/node/rpc-reference): Node RPC Reference description - \[Optimistic Ethereum Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/optimism-mainnet): Explore Optimistic Ethereum JSON-RPC methods via Tenderly Node RPC. Connect to Optimistic Ethereum (chain ID: 10) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Optimistic Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/optimism-sepolia): Explore Optimistic Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Optimistic Sepolia (chain ID: 11155420) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Plasma Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/plasma): Explore Plasma JSON-RPC methods via Tenderly Node RPC. Connect to Plasma (chain ID: 9745) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Plasma Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/plasma-testnet): Explore Plasma Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Plasma Testnet (chain ID: 9746) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Polygon Amoy Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/polygon-amoy): Explore Polygon Amoy JSON-RPC methods via Tenderly Node RPC. Connect to Polygon Amoy (chain ID: 80002) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Polygon Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/polygon-mainnet): Explore Polygon JSON-RPC methods via Tenderly Node RPC. Connect to Polygon (chain ID: 137) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Pricing and usage limits\](https://docs.tenderly.co/node/pricing): Learn how your Node RPC usage is calculated in Tenderly Units (TUs) for read, write, compute, and advanced compute requests. - \[Quickstart Querying blockchain data\](https://docs.tenderly.co/node/rpc-request-builder): Send RPC requests to Node RPC RPCs from the browser and create request collections. - \[RainbowKit - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/rainbow-kit): Learn how to configure Node RPC as an RPC provider in your RainbowKit components. - \[Reown AppKit - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/reown-app-kit): Learn how to configure Node RPC as an RPC provider for Reown AppKit. - \[Ronin Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ronin): Explore Ronin JSON-RPC methods via Tenderly Node RPC. Connect to Ronin (chain ID: 2020) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Ronin Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/ronin-testnet): Explore Ronin Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Ronin Testnet (chain ID: 202601) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Scroll Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/scroll-mainnet): Explore Scroll Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to Scroll Mainnet (chain ID: 534352) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Scroll Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/scroll-sepolia): Explore Scroll Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Scroll Sepolia (chain ID: 534351) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Soneium Minato Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/soneium-minato): Explore Soneium Minato JSON-RPC methods via Tenderly Node RPC. Connect to Soneium Minato (chain ID: 1946) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Soneium Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/soneium): Explore Soneium JSON-RPC methods via Tenderly Node RPC. Connect to Soneium (chain ID: 1868) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Sonic Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/sonic): Explore Sonic JSON-RPC methods via Tenderly Node RPC. Connect to Sonic (chain ID: 146) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Stable Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/stable): Explore Stable JSON-RPC methods via Tenderly Node RPC. Connect to Stable (chain ID: 988) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Stable Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/stable-testnet): Explore Stable Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Stable Testnet (chain ID: 2201) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Swellchain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/swellchain): Explore Swellchain JSON-RPC methods via Tenderly Node RPC. Connect to Swellchain (chain ID: 1923) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Swellchain Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/swellchain-sepolia): Explore Swellchain Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Swellchain Sepolia (chain ID: 1924) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Taiko Hoodi Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/taiko-hoodi): Explore Taiko Hoodi JSON-RPC methods via Tenderly Node RPC. Connect to Taiko Hoodi (chain ID: 167013) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Taiko Mainnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/taiko): Explore Taiko Mainnet JSON-RPC methods via Tenderly Node RPC. Connect to Taiko Mainnet (chain ID: 167000) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Tempo Moderato Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/tempo-moderato-testnet): Explore Tempo Moderato Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Tempo Moderato Testnet (chain ID: 42431) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ThirdWeb SDK - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/thirdweb-sdk) - \[Unichain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/unichain): Explore Unichain JSON-RPC methods via Tenderly Node RPC. Connect to Unichain (chain ID: 130) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Unichain Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/unichain-sepolia): Explore Unichain Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to Unichain Sepolia (chain ID: 1301) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Viem - Node RPC Integration\](https://docs.tenderly.co/node/integrations-chain-interaction/viem): Learn how to connect Viem to Node RPC to query EVM blockchains, send, trace, and simulate transactions. - \[Wagmi - Node RPC Integration\](https://docs.tenderly.co/node/integrations-dapp-ui/wagmi): Learn how to configure Node RPC as an RPC provider in your Wagmi hooks, components, and modals. - \[Web3.py - Node RPC Integration\](https://docs.tenderly.co/node/integrations-chain-interaction/web3-py): Learn how to use Web3.py to enable your Python application to communicate with Ethereum through Node RPC. - \[WebSockets\](https://docs.tenderly.co/node/guides/websockets): Tenderly WebSockets offer fast access to Ethereum's JSON-RPC and provide developers with a stable and persistent connection to Node RPC. - \[World Chain Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/worldchain-mainnet): Explore World Chain JSON-RPC methods via Tenderly Node RPC. Connect to World Chain (chain ID: 480) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[World Chain Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/worldchain-sepolia): Explore World Chain Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to World Chain Sepolia (chain ID: 4801) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[X Layer Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/xlayer): Explore X Layer JSON-RPC methods via Tenderly Node RPC. Connect to X Layer (chain ID: 196) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[X Layer Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/xlayer-testnet): Explore X Layer Testnet JSON-RPC methods via Tenderly Node RPC. Connect to X Layer Testnet (chain ID: 1952) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Zircuit Garfield Testnet Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/zircuit-garfield-testnet): Explore Zircuit Garfield Testnet JSON-RPC methods via Tenderly Node RPC. Connect to Zircuit Garfield Testnet (chain ID: 48898) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[Zircuit Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/zircuit): Explore Zircuit JSON-RPC methods via Tenderly Node RPC. Connect to Zircuit (chain ID: 48900) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ZKsync Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/zksync): Explore ZKsync JSON-RPC methods via Tenderly Node RPC. Connect to ZKsync (chain ID: 324) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. - \[ZKsync Sepolia Reference - Node RPC\](https://docs.tenderly.co/node/rpc-reference/zksync-sepolia): Explore ZKsync Sepolia JSON-RPC methods via Tenderly Node RPC. Connect to ZKsync Sepolia (chain ID: 300) with HTTP or WebSocket and access standard and Tenderly-enhanced RPC methods. ## RPC Method Reference Canonical JSON-RPC method pages (shown for ethereum-mainnet; the same methods are available across all supported networks — see Supported Networks). - \[debug\_traceBlock\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/debug\_traceBlock): debug\_traceBlock JSON-RPC method reference - \[debug\_traceBlockByHash\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/debug\_traceBlockByHash): debug\_traceBlockByHash JSON-RPC method reference - \[debug\_traceBlockByNumber\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/debug\_traceBlockByNumber): debug\_traceBlockByNumber JSON-RPC method reference - \[debug\_traceCall\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/debug\_traceCall): debug\_traceCall JSON-RPC method reference - \[debug\_traceTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/debug\_traceTransaction): debug\_traceTransaction JSON-RPC method reference - \[eth\_accounts\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_accounts): eth\_accounts JSON-RPC method reference - \[eth\_blockNumber\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_blockNumber): eth\_blockNumber JSON-RPC method reference - \[eth\_call\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_call): eth\_call JSON-RPC method reference - \[eth\_chainId\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_chainId): eth\_chainId JSON-RPC method reference - \[eth\_coinbase\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_coinbase): eth\_coinbase JSON-RPC method reference - \[eth\_createAccessList\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_createAccessList): eth\_createAccessList JSON-RPC method reference - \[eth\_estimateGas\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_estimateGas): eth\_estimateGas JSON-RPC method reference - \[eth\_feeHistory\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_feeHistory): eth\_feeHistory JSON-RPC method reference - \[eth\_gasPrice\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_gasPrice): eth\_gasPrice JSON-RPC method reference - \[eth\_getBalance\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBalance): eth\_getBalance JSON-RPC method reference - \[eth\_getBlockByHash\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBlockByHash): eth\_getBlockByHash JSON-RPC method reference - \[eth\_getBlockByNumber\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBlockByNumber): eth\_getBlockByNumber JSON-RPC method reference - \[eth\_getBlockReceipts\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBlockReceipts): eth\_getBlockReceipts JSON-RPC method reference - \[eth\_getBlockTransactionCountByHash\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBlockTransactionCountByHash): eth\_getBlockTransactionCountByHash JSON-RPC method reference - \[eth\_getBlockTransactionCountByNumber\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getBlockTransactionCountByNumber): eth\_getBlockTransactionCountByNumber JSON-RPC method reference - \[eth\_getCode\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getCode): eth\_getCode JSON-RPC method reference - \[eth\_getFilterChanges\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getFilterChanges): eth\_getFilterChanges JSON-RPC method reference - \[eth\_getFilterLogs\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getFilterLogs): eth\_getFilterLogs JSON-RPC method reference - \[eth\_getLogs\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getLogs): eth\_getLogs JSON-RPC method reference - \[eth\_getProof\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getProof): eth\_getProof JSON-RPC method reference - \[eth\_getStorageAt\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getStorageAt): eth\_getStorageAt JSON-RPC method reference - \[eth\_getTransactionByBlockHashAndIndex\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getTransactionByBlockHashAndIndex): eth\_getTransactionByBlockHashAndIndex JSON-RPC method reference - \[eth\_getTransactionByBlockNumberAndIndex\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getTransactionByBlockNumberAndIndex): eth\_getTransactionByBlockNumberAndIndex JSON-RPC method reference - \[eth\_getTransactionByHash\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getTransactionByHash): eth\_getTransactionByHash JSON-RPC method reference - \[eth\_getTransactionCount\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getTransactionCount): eth\_getTransactionCount JSON-RPC method reference - \[eth\_getTransactionReceipt\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getTransactionReceipt): eth\_getTransactionReceipt JSON-RPC method reference - \[eth\_getUncleByBlockHashAndIndex\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getUncleByBlockHashAndIndex): eth\_getUncleByBlockHashAndIndex JSON-RPC method reference - \[eth\_getUncleByBlockNumberAndIndex\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getUncleByBlockNumberAndIndex): eth\_getUncleByBlockNumberAndIndex JSON-RPC method reference - \[eth\_getUncleCountByBlockHash\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getUncleCountByBlockHash): eth\_getUncleCountByBlockHash JSON-RPC method reference - \[eth\_getUncleCountByBlockNumber\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_getUncleCountByBlockNumber): eth\_getUncleCountByBlockNumber JSON-RPC method reference - \[eth\_hashrate\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_hashrate): eth\_hashrate JSON-RPC method reference - \[eth\_maxPriorityFeePerGas\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_maxPriorityFeePerGas): eth\_maxPriorityFeePerGas JSON-RPC method reference - \[eth\_mining\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_mining): eth\_mining JSON-RPC method reference - \[eth\_newBlockFilter\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_newBlockFilter): eth\_newBlockFilter JSON-RPC method reference - \[eth\_newFilter\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_newFilter): eth\_newFilter JSON-RPC method reference - \[eth\_newPendingTransactionFilter\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_newPendingTransactionFilter): eth\_newPendingTransactionFilter JSON-RPC method reference - \[eth\_protocolVersion\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_protocolVersion): eth\_protocolVersion JSON-RPC method reference - \[eth\_sendRawTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_sendRawTransaction): eth\_sendRawTransaction JSON-RPC method reference - \[eth\_sendTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_sendTransaction): eth\_sendTransaction JSON-RPC method reference - \[eth\_sign\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_sign): eth\_sign JSON-RPC method reference - \[eth\_signTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_signTransaction): eth\_signTransaction JSON-RPC method reference - \[eth\_subscribe\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_subscribe): eth\_subscribe JSON-RPC method reference - \[eth\_syncing\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_syncing): eth\_syncing JSON-RPC method reference - \[eth\_uninstallFilter\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_uninstallFilter): eth\_uninstallFilter JSON-RPC method reference - \[eth\_unsubscribe\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/eth\_unsubscribe): eth\_unsubscribe JSON-RPC method reference - \[net\_listening\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/net\_listening): net\_listening JSON-RPC method reference - \[net\_peerCount\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/net\_peerCount): net\_peerCount JSON-RPC method reference - \[net\_version\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/net\_version): net\_version JSON-RPC method reference - \[tenderly\_decodeError\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_decodeError): tenderly\_decodeError JSON-RPC method reference - \[tenderly\_decodeEvent\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_decodeEvent): tenderly\_decodeEvent JSON-RPC method reference - \[tenderly\_decodeInput\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_decodeInput): tenderly\_decodeInput JSON-RPC method reference - \[tenderly\_errorSignatures\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_errorSignatures): tenderly\_errorSignatures JSON-RPC method reference - \[tenderly\_estimateGas\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_estimateGas): tenderly\_estimateGas JSON-RPC method reference - \[tenderly\_estimateGasBundle\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_estimateGasBundle): tenderly\_estimateGasBundle JSON-RPC method reference - \[tenderly\_eventSignature\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_eventSignature): tenderly\_eventSignature JSON-RPC method reference - \[tenderly\_functionSignatures\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_functionSignatures): tenderly\_functionSignatures JSON-RPC method reference - \[tenderly\_gasPrice\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_gasPrice): tenderly\_gasPrice JSON-RPC method reference - \[tenderly\_getContractAbi\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_getContractAbi): tenderly\_getContractAbi JSON-RPC method reference - \[tenderly\_getStorageChanges\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_getStorageChanges): tenderly\_getStorageChanges JSON-RPC method reference - \[tenderly\_getTransactionsRange\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_getTransactionsRange): tenderly\_getTransactionsRange JSON-RPC method reference - \[tenderly\_simulateBundle\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_simulateBundle): tenderly\_simulateBundle JSON-RPC method reference - \[tenderly\_simulateTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_simulateTransaction): tenderly\_simulateTransaction JSON-RPC method reference - \[tenderly\_suggestGasFee\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_suggestGasFee): tenderly\_suggestGasFee JSON-RPC method reference - \[tenderly\_traceTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/tenderly\_traceTransaction): tenderly\_traceTransaction JSON-RPC method reference - \[trace\_block\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_block): trace\_block JSON-RPC method reference - \[trace\_call\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_call): trace\_call JSON-RPC method reference - \[trace\_callMany\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_callMany): trace\_callMany JSON-RPC method reference - \[trace\_filter\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_filter): trace\_filter JSON-RPC method reference - \[trace\_get\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_get): trace\_get JSON-RPC method reference - \[trace\_replayBlockTransactions\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_replayBlockTransactions): trace\_replayBlockTransactions JSON-RPC method reference - \[trace\_replayTransaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_replayTransaction): trace\_replayTransaction JSON-RPC method reference - \[trace\_transaction\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/trace\_transaction): trace\_transaction JSON-RPC method reference - \[web3\_clientVersion\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/web3\_clientVersion): web3\_clientVersion JSON-RPC method reference - \[web3\_sha3\](https://docs.tenderly.co/node/rpc-reference/ethereum-mainnet/web3\_sha3): web3\_sha3 JSON-RPC method reference ## Web3 Actions - \[Action Execution\](https://docs.tenderly.co/web3-actions/references/action-execution): Learn about execution modes and status types for Web3 Actions in Tenderly to manage and troubleshoot your actions effectively. - \[Action Functions, Events, and Triggers\](https://docs.tenderly.co/web3-actions/references/action-functions-events-and-triggers): Explore Web3 Actions core elements, configure triggers for supported events, and link triggers to action functions in tenderly.yaml. - \[CLI Cheatsheet\](https://docs.tenderly.co/web3-actions/references/cli-cheatsheet): >- - \[Context: Gateway, Storage, Secrets\](https://docs.tenderly.co/web3-actions/references/context-storage-and-secrets): Access blockchain via Node RPC, store and fetch data from Storage, and save sensitive information like API keys in Secrets. - \[Deploy Web3 Action via CLI\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/deploy-web3-action-via-cli): Get started with building Web3 Actions using the Tenderly CLI step by step. - \[Deploy Web3 Actions via Dashboard\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/deploy-web3-actions-via-dashboard): Build and deploy a Web3 Action using the Web3 Action builder in the Tenderly Dashboard. - \[Discord Alerts for New Uniswap Pools\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/how-to-send-a-discord-message-about-a-new-uniswap-pool): >- - \[Error Reporting\](https://docs.tenderly.co/web3-actions/references/error-reporting): Access the Error Reporting section for Web3 Action execution incidents. Filter incidents by parameters and re-run failed ones. - \[How to Access Node RPC from Web3 Actions\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/how-to-access-web3-gateway-from-web3-actions): >- - \[How to Build a Custom Oracle\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/how-to-build-a-custom-oracle): >- - \[How to Handle On-Chain Events\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/how-to-handle-on-chain-events): Use Web3 Actions as a serverless backend to respond to on-chain events. Follow a Tic-Tac-Toe example to monitor game changes. - \[Intro to Web3 Actions\](https://docs.tenderly.co/web3-actions/intro-to-web3-actions): Deploy custom JS/TS functions that hook into on-chain events to build active monitoring, serverless dapp backends, and service integrations. - \[Lido Validator Exit Notifications\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/monitoring-network-validators-exits): Learn how to use Tenderly Web3 Actions to monitor Lido validator exit requests and send notifications via Telegram using open-source monitoring template. - \[Local Development and Testing\](https://docs.tenderly.co/web3-actions/references/local-development-and-testing): Achieve faster iteration on Web3 Action code and write automated tests for your action functions using @tenderly/actions-test. - \[Manage Web3 Actions Lifecycle\](https://docs.tenderly.co/web3-actions/references/stopping-upgrading-and-manually-running-web3-actions): Operate your Web3 Actions using the Tenderly Dashboard. Learn how to stop, upgrade, or manually run a Web3 Action. - \[Modular Monitoring with Web3Actions\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/modular-web3-action): Web3Actions as a most flexible monitoring tool you'll ever need - \[Monitor UniswapV3 Pool Creation\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts/monitor-uniswapV3-pools): Learn how to use Tenderly Web3 Actions to monitor new pool creations in UniswapV3Factory and perform automated actions. - \[Networks\](https://docs.tenderly.co/web3-actions/references/networks): Get an overview of network IDs you can use to configure your Web3 Action triggers. - \[Node RPC Access\](https://docs.tenderly.co/web3-actions/references/web3-gateway-access): Learn how to set up a Web3 Action with access to the Mainnet through Node RPC. - \[Notifications\](https://docs.tenderly.co/web3-actions/references/notifications): Set up notifications for failed Web3 Actions and follow a step-by-step guide to configure email alert destinations in Tenderly. - \[Project Structure\](https://docs.tenderly.co/web3-actions/references/project-structure): >- - \[References\](https://docs.tenderly.co/web3-actions/references): Find everything you need to create, operate, and troubleshoot Web3 Actions. - \[Tutorials and Quickstarts\](https://docs.tenderly.co/web3-actions/tutorials-and-quickstarts): Find a list of helpful Web3 Action quickstarts and step-by-step tutorials. - \[Usage Rate Limits\](https://docs.tenderly.co/web3-actions/usage-rate-limits): Get a short overview of Web3 Action execution rate limits. ## Developer Explorer - \[Developer Explorer\](https://docs.tenderly.co/developer-explorer) - \[Fund Flow\](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow): Visualize token transfers as an interactive graph. Trace asset paths, filter by token or address, inspect net positions, and jump to the execution trace. - \[Smart Contracts\](https://docs.tenderly.co/developer-explorer/contracts): Learn how to add and manage contracts in Tenderly. - \[Transaction Listing\](https://docs.tenderly.co/developer-explorer/transaction-listing): A guide to managing and analyzing transactions in the Tenderly Dashboard for development and monitoring. - \[Transactions\](https://docs.tenderly.co/developer-explorer/inspect-transaction): A guide to managing and analyzing transactions in the Tenderly Dashboard for development and monitoring. - \[Wallets\](https://docs.tenderly.co/developer-explorer/wallets) ## MCP Server - \[MCP Server\](https://docs.tenderly.co/mcp-server): Connect Claude and other AI assistants to Tenderly — Virtual Environments, simulations, tracing, contract inspection, and VNet RPC tools through the Model Context Protocol. - \[MCP Server Examples\](https://docs.tenderly.co/mcp-server/examples): Step-by-step walkthroughs for common workflows using the Tenderly MCP Server with Claude. - \[MCP Server Quickstart\](https://docs.tenderly.co/mcp-server/quickstart): Connect the Tenderly MCP Server to Claude Code, Claude.ai, Claude Desktop, and other MCP clients. - \[MCP Server Tools Reference\](https://docs.tenderly.co/mcp-server/tools): Complete reference for all 43 tools available in the Tenderly MCP Server. ## Debugger - \[All About the Via-Ir Pipeline\](https://docs.tenderly.co/debugger/via-ir-pipeline): Learn what the via-ir pipeline is, how it works, and the common challenges when parsing via-ir-compiled Solidity contracts. - \[Dev Toolkit Browser Extension\](https://docs.tenderly.co/debugger/dev-toolkit-browser-extension): Dev Toolkit browser extension gives one-click access to Tenderly debugging tools on any block explorer to analyze on-chain data. - \[Evaluate Expressions with Advanced Debugger\](https://docs.tenderly.co/debugger/evaluate-expressions-with-advanced-debugger): Trace Eval - \[Gas Profiler\](https://docs.tenderly.co/debugger/gas-profiler) - \[How to Use Tenderly Debugger\](https://docs.tenderly.co/debugger): Transactions debugger, smart contract debugger - \[Investigating a Failed Transaction\](https://docs.tenderly.co/debugger/guides/investigating-a-failed-transaction) - \[Investigating a Hack (Cover Protocol)\](https://docs.tenderly.co/debugger/guides/investigating-a-hack-cover-protocol) - \[War Room Aid Kit\](https://docs.tenderly.co/debugger/war-room-aid-kit) ## Simulations - \[Asset and Balance Changes\](https://docs.tenderly.co/simulations/asset-balance-changes): Access token data and dollar value changes from the asset\_changes object returned by Simulation API and Transaction Trace. - \[Bundled Simulations\](https://docs.tenderly.co/simulations/bundled-simulations): Learn how to simulate multiple transactions in a single API or RPC request. - \[Dry-Run User Transactions\](https://docs.tenderly.co/simulations/guides/dry-run-user-transactions): >- - \[Gas Estimation\](https://docs.tenderly.co/simulations/gas-estimation): Learn how to estimate precise gas limits for transaction simulations. - \[MetaMask Snap Transaction Preview\](https://docs.tenderly.co/simulations/guides/how-to-add-transaction-preview-to-a-metamask-snap-using-tenderly-simulation-api): Add transaction preview to MetaMask via a Snap using the Tenderly Simulation API so users can preview outcomes before signing. - \[Rabby Wallet Transaction Preview\](https://docs.tenderly.co/simulations/guides/how-to-add-transaction-preview-to-a-rabby-wallet-using-tenderly-simulation-api): Add transaction preview to Rabby Wallet using the Tenderly Simulation API so users can preview outcomes before sending on-chain. - \[Simulation API With State Overrides\](https://docs.tenderly.co/simulations/state-overrides): Learn how to use state overrides to modify smart contract states. - \[Simulation Modes\](https://docs.tenderly.co/simulations/simulation-modes): Choose full mode for complete decoding, abi mode for partial decoding, or quick mode for faster raw transaction outputs. - \[Simulations Guides\](https://docs.tenderly.co/simulations/guides): Follow step-by-step guides on how to introduce simulations into your project. - \[Simulations Overview\](https://docs.tenderly.co/simulations): Simulate single or bundled transactions via API or RPC with decoded traces, accurate gas estimates, balance changes, and more. - \[Simulations Quickstart\](https://docs.tenderly.co/simulations/quickstart): Learn how to simulate single transactions via Tenderly RPC and API. - \[Single Simulations\](https://docs.tenderly.co/simulations/single-simulations): Learn how to simulate a single transaction via RPC and API. - \[Transaction Preview\](https://docs.tenderly.co/simulations/transaction-preview): Learn how the add a Transaction Preview option to your dapp or wallet powered by Tenderly's Simulation API. - \[Using Simulation RPC in Dapp UI\](https://docs.tenderly.co/simulations/guides/using-simulation-rpc-in-dapp-ui): Integrate transaction simulations into your dapp via Tenderly Simulation RPC. Follow a step-by-step Uniswap UI integration example. ## Simulator UI - \[Editing Contract Source\](https://docs.tenderly.co/simulator-ui/editing-contract-source) - \[Pending vs Historical Block\](https://docs.tenderly.co/simulator-ui/pending-vs-historical-block) - \[Simulation Parameters\](https://docs.tenderly.co/simulator-ui/transaction-parameters) - \[Simulation UI With State Overrides\](https://docs.tenderly.co/simulator-ui/simulation-ui-with-state-overrides): >- - \[Simulator UI Overview\](https://docs.tenderly.co/simulator-ui): Use the Tenderly Simulator UI to build transaction simulations with decoded traces, gas estimates, balance changes, and more. - \[Using Simulation UI\](https://docs.tenderly.co/simulator-ui/using-simulation-ui): Follow a step-by-step example of using the Simulation UI. ## Tenderly SDK - \[Basic Concepts & FAQs\](https://docs.tenderly.co/tenderly-sdk/basic-concepts-and-faqs): >- - \[Intro to Tenderly SDK\](https://docs.tenderly.co/tenderly-sdk/intro-to-tenderly-sdk): With the Tenderly SDK, you can simulate individual transactions or bundles of transactions, manage contracts and wallets, and verify contracts from your code. - \[Managing Contracts\](https://docs.tenderly.co/tenderly-sdk/managing-contracts): >- - \[Managing Wallets\](https://docs.tenderly.co/tenderly-sdk/managing-wallets): >- - \[Practical Examples\](https://docs.tenderly.co/tenderly-sdk/practical-examples): >- - \[Simulate Transactions via SDK\](https://docs.tenderly.co/tenderly-sdk/tutorials-and-quickstarts/how-to-simulate-transactions-with-tenderly-sdk): Learn how to execute a simple transaction simulation using the Tenderly SDK. - \[Simulating Transactions\](https://docs.tenderly.co/tenderly-sdk/simulating-transactions): >- - \[Simulation Bundles with SDK\](https://docs.tenderly.co/tenderly-sdk/tutorials-and-quickstarts/how-to-perform-simulation-bundles-with-tenderly-sdk): Learn how to execute a transaction bundle with Simulation Bundles using the Tenderly SDK. - \[Tutorials and Quickstarts\](https://docs.tenderly.co/tenderly-sdk/tutorials-and-quickstarts): >- ## Contract Verification - \[Smart Contract Verification\](https://docs.tenderly.co/contract-verification): Learn how to verify smart contracts to unlock the full power of Tenderly's development tooling. - \[Smart Contract Verification Using Foundry\](https://docs.tenderly.co/contract-verification/foundry): Learn how to use Foundry to verify a smart contract on a public Tenderly Virtual Environment. - \[Smart Contract Verification Using Hardhat\](https://docs.tenderly.co/contract-verification/hardhat): Learn how to use the Tenderly-Hardhat plugin to perform automatic and manual smart contract verification. - \[Verify Contracts via Dashboard\](https://docs.tenderly.co/contract-verification/dashboard): Learn how to verify smart contracts publicly and privately in the browser through the Tenderly Dashboard. - \[Verifying Proxy Contracts\](https://docs.tenderly.co/contract-verification/hardhat-proxy-contracts): Follow this step-by-step guide to learn about verifying proxy smart contracts using the Tenderly-Hardhat plugin. ## Admin RPC - \[Custom RPC Methods\](https://docs.tenderly.co/network-customization-rpc): Explore the list of network customization RPC methods available in Virtual Environments. Use these methods to manipulate network state, balances, and history. ## Alerts - \[Account-Scoped\](https://docs.tenderly.co/alerts/configuring-alert-destinations/account-scoped): This page walks you through how to create each account-scoped Alert Destination. - \[Alert Destinations\](https://docs.tenderly.co/alerts/configuring-alert-destinations): Configure alert destinations like email, Slack, and webhooks to receive notifications when your Tenderly alerts trigger. - \[Alert Types, Targets, and Parameters\](https://docs.tenderly.co/alerts/alert-types-targets-and-parameters): Set up and configure alert types from the Tenderly Dashboard to get notified when specific on-chain events occur on your contracts. - \[Alerting Quickstart Guide\](https://docs.tenderly.co/alerts/tutorials-and-quickstarts/alerting-quickstart-guide): Learn how to set up, configure, and manage an Alert in a few easy steps. - \[How to Use Webhooks for Alerting\](https://docs.tenderly.co/alerts/tutorials-and-quickstarts/how-to-use-webhooks-for-alerting): Learn how to create your first webhook and start receiving alerting events. - \[Intro to Alerts\](https://docs.tenderly.co/alerts/intro-to-alerts): Listen for on-chain events and receive real-time notifications via email, Slack, PagerDuty, and other alert destinations. - \[Project-Scoped\](https://docs.tenderly.co/alerts/configuring-alert-destinations/project-scoped): This page walks you through how to create each project-scoped Alert Destination. - \[Setting Up Alerts as Triggers for Web3Actions\](https://docs.tenderly.co/alerts/configuring-alert-destinations/alert-web3action): Learn how to set up and configure Alerts as triggers for Web3Actions in Tenderly, enabling automated responses to blockchain events. - \[Tutorials and Quickstarts\](https://docs.tenderly.co/alerts/tutorials-and-quickstarts): Here you can find comprehensive tutorials and practical guides that show you how to set up, configure, and manage Tenderly Alerts. - \[Using Alerts API\](https://docs.tenderly.co/alerts/api): Set up simple and complex alerts in Tenderly using Alerts API ## Monitoring - \[Converting Contracts into Wallets\](https://docs.tenderly.co/monitoring/wallets/converting-contracts-into-wallets) - \[Integrations\](https://docs.tenderly.co/monitoring/integrations) - \[Proxy Contracts\](https://docs.tenderly.co/monitoring/smart-contracts/proxy-contracts) - \[Public Contracts\](https://docs.tenderly.co/monitoring/smart-contracts/public-contracts) - \[Simulations with a Wallet\](https://docs.tenderly.co/monitoring/wallets/simulations-with-a-wallet) - \[Transaction Overview\](https://docs.tenderly.co/monitoring/contracts) - \[Wallet Public Page\](https://docs.tenderly.co/monitoring/wallets/wallet-public-page) - \[Wallet Tags\](https://docs.tenderly.co/monitoring/wallets/wallet-tags) ## Account Management - \[Account Management\](https://docs.tenderly.co/account): Learn how to manage your Tenderly account, projects, and team members. - \[Account Slug and Project Slug\](https://docs.tenderly.co/account/projects/account-project-slug): Learn how to find the account and project slugs for use in various configuration files. - \[Add Member\](https://docs.tenderly.co/account/organizations/organization-members): Learn how to add team members to an organization. - \[Create a Tenderly Project\](https://docs.tenderly.co/account/projects): Learn how to create a project in Tenderly. - \[Generate and Manage API Access Tokens\](https://docs.tenderly.co/account/projects/how-to-generate-api-access-token): Learn how to generate API access tokens for personal accounts and organizations. - \[Organizations and Team Members\](https://docs.tenderly.co/account/organizations): Learn how to set up an organization, add team members, and manage permissions. - \[Project Settings\](https://docs.tenderly.co/account/projects/project-settings): Learn how to change project settings. ## Guides - \[Guides\](https://docs.tenderly.co/guides): Learn how to use Tenderly by following our official guides and tutorials. ## API Reference - \[API Reference\](https://docs.tenderly.co/reference/api): Explore Tenderly's API reference and learn how to manage Simulations, Alerts, Web3 Actions and more. - \[API Reference\](https://docs.tenderly.co/reference): Explore Tenderly APIs and Node RPC JSON-RPC references. ## FAQ - \[FAQ\](https://docs.tenderly.co/faq): Get answers to the most frequently asked questions about Tenderly. - \[FAQ: Account\](https://docs.tenderly.co/faq/account): Managing your Tenderly account. - \[FAQ: Alerts\](https://docs.tenderly.co/faq/alerts): Creating and managing on-chain Alerts. - \[FAQ: API\](https://docs.tenderly.co/faq/api): Interacting with Tenderly APIs. - \[FAQ: Billing\](https://docs.tenderly.co/faq/billing): Upgrading and downgrading your Tenderly subscription. - \[FAQ: Contract Verification\](https://docs.tenderly.co/faq/contract-verification): Verifying smart contracts using Tenderly. - \[FAQ: Node\](https://docs.tenderly.co/faq/node): Accessing the blockchain using Node RPC. - \[FAQ: Projects\](https://docs.tenderly.co/faq/projects): Setting up projects on Tenderly. - \[FAQ: Simulations\](https://docs.tenderly.co/faq/simulations): Simulating transactions with Tenderly. - \[FAQ: Virtual Environments\](https://docs.tenderly.co/faq/virtual-environments): Creating and managing Virtual Environments - \[FAQ: Web3 Actions\](https://docs.tenderly.co/faq/web3-actions): Understanding how Web3 Actions work. ## Workshops - \[Act 0: Warmup\](https://docs.tenderly.co/workshops/virtual-environments/act-0): Set up your environment and prerequisites for the Virtual Environments workshop. - \[Act 1: Local project setup\](https://docs.tenderly.co/workshops/virtual-environments/act-1): Set up your local project for the Virtual Environments workshop. - \[Act 2: Running it locally\](https://docs.tenderly.co/workshops/virtual-environments/act-2): Deploy contracts to Virtual Environment and run the UI locally. - \[Act 4: CI\](https://docs.tenderly.co/workshops/virtual-environments/act-4): Set up GitHub Actions for continuous integration with Virtual Environments. - \[Act 5: Enabling verification\](https://docs.tenderly.co/workshops/virtual-environments/act-5): Configure Hardhat verification for your Virtual Environment staging environments. - \[Creating staging environments\](https://docs.tenderly.co/workshops/virtual-environments/act-3): Creating staging environments - \[Intermezzo: Verification\](https://docs.tenderly.co/workshops/virtual-environments/intermezzo): Set up contract verification with Tenderly CLI for Virtual Environments. - \[Staging in Web3\](https://docs.tenderly.co/workshops/virtual-environments): Staging in Web3 Workshop - \[Workshop complete\](https://docs.tenderly.co/workshops/virtual-environments/done): You've finished the Staging in Web3 workshop — a recap of what you learned.

---

# Changelog - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/changelog/overview#content-area)

FiltersClear

Virtual EnvironmentsMultichainBridges

The latest product updates, features, and fixes. For deeper announcements, see the [Tenderly blog](https://blog.tenderly.co/)
.

[​](https://docs.tenderly.co/changelog/overview#june-9-2026)

June 9, 2026

Virtual EnvironmentsMultichainBridges

[​](https://docs.tenderly.co/changelog/overview#new)

New
-----------------------------------------------------------

**Multichain Virtual Environments now span 100+ EVM networks.** A single Virtual Environment can attach Ethereum, Arbitrum, Optimism, Base, and any of 100+ supported EVM networks under one shared identity, with a unified cross-chain timeline. See [Multichain Virtual Environments](https://docs.tenderly.co/virtual-environments/multichain/overview)
.**Multichain contract deployment.** Deploy and test contracts across multiple chains simultaneously from one Virtual Environment, useful for cross-chain protocol testing, CI/CD pipelines, and staging environments without real funds. See [common uses](https://docs.tenderly.co/virtual-environments/multichain/overview#common-uses)
.

[​](https://docs.tenderly.co/changelog/overview#updates)

Updates
-------------------------------------------------------------------

**Simpler Bridge Module setup.** Enable the Bridge Module from the Virtual Environment **Settings** page under the **Advanced** panel, with no separate Bridge settings tab required. Relay covers LayerZero, Chainlink CCIP, Across, and CCTP on supported networks. See [Bridges](https://docs.tenderly.co/virtual-environments/multichain/bridges)
.**Network Mirror Mode transaction list: no row cap.** Browse the full transaction history of a Mirror-Mode Virtual Environment without a 100-row limit. See [Network Mirror Mode](https://docs.tenderly.co/virtual-environments/network-mirror-mode)
.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Changelog - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/hi/changelog/overview#content-area)

फिल्टर्सक्लियर फिल्टर्स

Virtual EnvironmentsMultichainBridges

नवीनतम उत्पाद अपडेट, सुविधाएँ, और फिक्स। गहरी घोषणाओं के लिए, [Tenderly blog](https://blog.tenderly.co/)
 देखें।

[​](https://docs.tenderly.co/hi/changelog/overview#june-9-2026)

June 9, 2026

Virtual EnvironmentsMultichainBridges

[​](https://docs.tenderly.co/hi/changelog/overview#%E0%A4%A8%E0%A4%AF%E0%A4%BE)

नया
--------------------------------------------------------------------------------------

**Multichain Virtual Environments अब 100+ EVM नेटवर्क पर फैले हैं।** एक अकेला Virtual Environment Ethereum, Arbitrum, Optimism, Base, और 100+ समर्थित EVM नेटवर्क में से किसी को भी एक साझा पहचान के तहत जोड़ सकता है, एक एकीकृत cross-chain timeline के साथ। [Multichain Virtual Environments](https://docs.tenderly.co/virtual-environments/multichain/overview)
 देखें।**Multichain contract deployment।** एक Virtual Environment से कई chains पर एक साथ contracts deploy और test करें, cross-chain protocol परीक्षण, CI/CD pipelines, और वास्तविक funds के बिना staging परिवेश के लिए उपयोगी। [common uses](https://docs.tenderly.co/virtual-environments/multichain/overview#common-uses)
 देखें।

[​](https://docs.tenderly.co/hi/changelog/overview#%E0%A4%85%E0%A4%AA%E0%A4%A1%E0%A5%87%E0%A4%9F)

अपडेट
----------------------------------------------------------------------------------------------------------

**सरल Bridge Module सेटअप।** **Advanced** panel के तहत Virtual Environment **Settings** पेज से Bridge Module सक्षम करें, अलग Bridge settings tab की आवश्यकता के बिना। Relay समर्थित नेटवर्क पर LayerZero, Chainlink CCIP, Across, और CCTP को कवर करता है। [Bridges](https://docs.tenderly.co/virtual-environments/multichain/bridges)
 देखें।**Network Mirror Mode transaction सूची: कोई row cap नहीं।** 100-row सीमा के बिना Mirror-Mode Virtual Environment का पूरा transaction इतिहास ब्राउज़ करें। [Network Mirror Mode](https://docs.tenderly.co/virtual-environments/network-mirror-mode)
 देखें।

वाज़ दिस पेज हेल्पफुल

यसनो

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Uniswap V3 - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/defi-modules/uniswap#content-area)

When you navigate to a Uniswap V3 pool contract on a supported network, Tenderly recognizes the address and renders a pool page instead of the generic contract view. The page identifies the pool by protocol, token pair, and version, and presents pool data using Uniswap terminology.

Open a live Uniswap pool in Tenderly Console
--------------------------------------------

[​](https://docs.tenderly.co/defi-modules/uniswap#pool-header)

Pool header
-----------------------------------------------------------------------------

The header identifies the contract as a Uniswap V3 pool and shows the token pair (for example, WBTC / ETH), the protocol version tag, the network, and the pool address. A toggle next to the pair name inverts the token pair display, which flips the quote direction of the price chart and pair rate. The header presents the following pool metrics:

| Metric | Description |
| --- | --- |
| Fee APR (24H) | Annualized return from trading fees over the last 24 hours |
| Active liquidity | Dollar value of liquidity active at the current price |
| TVL | Total dollar value locked in the pool |
| Pool balances | Current holdings of each token in the pair, with a ratio bar |
| Volume (24H) | Dollar volume traded in the last 24 hours, with the swap count |
| Fees (24H) | Dollar value of fees generated in the last 24 hours |

Next to the metrics, a chart plots the pool over time with three views: **Price** (the pair exchange rate, with the current rate and percentage change), **Volume**, and **Liquidity**. A time range selector adjusts the window from one day up to all time.

[​](https://docs.tenderly.co/defi-modules/uniswap#transactions)

Transactions
-------------------------------------------------------------------------------

The Transactions tab lists recent pool activity. Each swap is classified with a directional label, **Buy** or **Sell**, expressed against the base token (for example, Buy WBTC or Sell WBTC), instead of a raw `swap` call signature. The table shows the transaction hash, the wallet that initiated the swap, the classification label, the time, the USD value, and the amount of each token in the pair. Transaction hashes link to the transaction detail page, and wallet addresses link to the wallet page. ![Recent activity on a Uniswap V3 WBTC/ETH pool with each transaction classified as Buy WBTC or Sell WBTC, alongside the wallet, USD value, and token amounts](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/uniswap-pool-transactions.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=21a398362e1f8375a799ad20f2d67a98)

[​](https://docs.tenderly.co/defi-modules/uniswap#protocol-overview)

Protocol overview
-----------------------------------------------------------------------------------------

The Protocol overview tab presents pool quality and market depth metrics:

| Metric | Description |
| --- | --- |
| Spot vs TWAP | Deviation between the spot price and the time-weighted average price |
| Oracle cardinality | Number of observation slots in the pool’s price oracle |
| Swaps (24H) | Swap count over the last 24 hours |
| Pool age | Time since pool creation |

Two market depth panels quantify how the pool absorbs trades:

*   **Pressure to move price ±1%**: the dollar value of buying or selling required to move the pool price up or down by one percent.
*   **Price impact at standard sizes**: the percentage price impact of trades at 10K,10K, 10K,100K, 1M,and1M, and 1M,and10M.

![Uniswap V3 pool Protocol overview tab showing spot vs TWAP, oracle cardinality, swap count, pool age, pressure to move price, and price impact at standard sizes](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/uniswap-pool-overview.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=d8a483bbcb993323b4da5861ddf946f3)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Aave V3 - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/defi-modules/aave#content-area)

When you navigate to a recognized Aave V3 reserve, Tenderly renders a reserve page instead of the generic contract view. The page identifies the reserve by protocol, reserve name, and version (for example, Aave USDC Reserve V3), and links to the underlying token.

Open a live Aave V3 pool in Tenderly Console
--------------------------------------------

[​](https://docs.tenderly.co/defi-modules/aave#reserve-header)

Reserve header
--------------------------------------------------------------------------------

The header presents the following reserve metrics:

| Metric | Description |
| --- | --- |
| Total supplied | Amount supplied against the supply cap, in dollars and tokens, with the utilization percentage |
| Supply APY | Current annualized yield for suppliers |
| Total borrowed | Amount borrowed against the borrow cap, with the utilization percentage |
| Borrow APY | Current annualized rate paid by borrowers |
| Reserve factor | Share of interest routed to the Aave treasury |

Next to the metrics, a chart plots **Supply APY** or **Borrow APY** over a selectable time range, with the average APY for the selected window.

[​](https://docs.tenderly.co/defi-modules/aave#transactions)

Transactions
----------------------------------------------------------------------------

The Transactions tab lists recent reserve activity. Each transaction is classified with an Aave action label: **Supply**, **Borrow**, **Repay**, or **Withdraw**. The table shows the transaction hash, the user wallet, the action, the time, and the amount in both tokens and dollars. ![Aave V3 USDC reserve showing total supplied, supply and borrow APY, reserve factor, the supply APY chart, and transactions classified as Supply, Borrow, Repay, and Withdraw](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/aave-pool-overview.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=aab378777e8b56095d918a515ef6d950)

[​](https://docs.tenderly.co/defi-modules/aave#protocol-overview)

Protocol overview
--------------------------------------------------------------------------------------

The Protocol overview tab is split into three views: Allocation, Performance, and Risk.

### 

[​](https://docs.tenderly.co/defi-modules/aave#allocation)

Allocation

The Allocation view renders a **Reserve backing** table with the reserve, its backing value, the supply cap, the borrow cap, and the average variable borrow APY. A Backing chart below the table plots the backing value over time. ![Aave V3 reserve Allocation view showing the Reserve backing table with backing value, supply cap, borrow cap, and average variable borrow APY](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/aave-overview-allocation.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=6409ee0b707190189646b717566decd5)

### 

[​](https://docs.tenderly.co/defi-modules/aave#performance)

Performance

The Performance view plots the **Liquidity index**, the cumulative interest accrued by the reserve since inception. Below the chart, a Returns panel lists the instant supply APY, instant borrow APY, and the trailing 7-day and 30-day APY values, and a Fees panel shows the reserve factor. ![Aave V3 reserve Performance view showing the liquidity index chart, instant and trailing APY values, and the reserve factor](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/aave-overview-performance.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=bb240a19a59fb3a24752ca17ee6138b2)

### 

[​](https://docs.tenderly.co/defi-modules/aave#risk)

Risk

The Risk view surfaces the reserve’s governance and access control state:

*   **Pool roles**: the ACL Admin, ACL Manager, and Emergency Admin addresses.
*   **Risk curation**: the Risk Admin and Risk Stewards addresses, where configured.
*   **Access**: a table mapping each adjustable parameter (such as the supply cap and borrow cap) to the role that can change it.

![Aave V3 reserve Risk view showing pool roles, risk curation addresses, and the access table mapping parameters to the roles that control them](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/aave-overview-risk.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=c1f92b3a527820f5b9a8a06768ca6b02)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Morpho - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/defi-modules/morpho#content-area)

When you navigate to a recognized Morpho vault, Tenderly renders a vault page instead of the generic contract view. The page identifies the vault by protocol, vault name, and version (for example, Morpho Steakhouse Prime USDC V2), and links to the underlying token.

Open a live Morpho vault in Tenderly Console
--------------------------------------------

[​](https://docs.tenderly.co/defi-modules/morpho#vault-header)

Vault header
------------------------------------------------------------------------------

The header presents the following vault metrics:

| Metric | Description |
| --- | --- |
| Total Deposits | Dollar and token value deposited in the vault |
| Liquidity | Value available for immediate withdrawal |
| Exposure | Number of markets the vault allocates to, with market icons |
| Net APY | Current annualized yield net of fees |
| Pending governance | Count of pending governance actions on the vault |

Next to the metrics, a chart plots the vault over time with three views: **Deposits**, **Net APY**, and **Share Price**. A denomination toggle switches values between the underlying token and USD, and a time range selector adjusts the window.

[​](https://docs.tenderly.co/defi-modules/morpho#transactions)

Transactions
------------------------------------------------------------------------------

The Transactions tab lists recent vault activity. Each transaction is classified with a vault action label: **Deposit** or **Withdraw**. The table shows the transaction hash, the user wallet, the action, the time, and the amount in both tokens and dollars. ![Morpho vault page showing the protocol badge, total deposits, liquidity, market exposure, net APY, pending governance, and transactions classified as Deposit and Withdraw](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-vault-overview.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=b26bdbe59826c97c11b1c9c80665a57c)

[​](https://docs.tenderly.co/defi-modules/morpho#protocol-overview)

Protocol overview
----------------------------------------------------------------------------------------

The Protocol overview tab is split into four views: Allocation, Performance, Risk, and User distribution.

### 

[​](https://docs.tenderly.co/defi-modules/morpho#allocation)

Allocation

The Allocation view renders an **Exposure** table listing every market the vault allocates to. For each market the table shows the allocation value, market liquidity, underlying liquidity, utilization, the absolute and relative caps, and the market APY. A chart below the table plots allocation over time, toggleable between absolute value and percentage. ![Morpho vault Allocation view showing the Exposure table with per-market allocation, liquidity, utilization, caps, and APY](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-overview-allocation.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=205cbd63dc4b03a48e081c5d46475d88)

### 

[​](https://docs.tenderly.co/defi-modules/morpho#performance)

Performance

The Performance view plots the **Position unit price**, the value of one vault share in the underlying token, with the current share price stated above the chart. Below it, a Returns panel lists the instant APY and the trailing 7-day, 30-day, and 90-day APY values, and a Fees panel shows the vault’s performance fee and management fee. ![Morpho vault Performance view showing the position unit price chart, instant and trailing APY values, and the performance and management fees](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-overview-performance.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=2baa3d0c2914267db2c0d30668acd276)

### 

[​](https://docs.tenderly.co/defi-modules/morpho#risk)

Risk

The Risk view surfaces the vault’s governance and timelock configuration:

*   **Vault roles**: the Owner, Curator, and Guardian addresses.
*   **Risk curation**: the allocator addresses authorized to rebalance the vault.
*   **Timelocks**: a table mapping each governance function (such as `addAdapter` or `removeAdapter`) to its timelock duration, including functions with no timelock and functions that have been abdicated.

![Morpho vault Risk view showing vault roles, allocator addresses, and the timelocks table mapping governance functions to their durations](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-overview-risk.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=412c6d6b8459642b5f67983d5d2a2e38)

### 

[​](https://docs.tenderly.co/defi-modules/morpho#user-distribution)

User distribution

The User distribution view lists the vault’s depositors. For each wallet the table shows the deposit amount in the underlying token and its percentage of total deposits. Wallet addresses link to their wallet pages. ![Morpho vault User distribution view listing depositor wallets with deposit amounts and percentage of total deposits](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-overview-users.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=2a5817c00d376889a4e5fdd18be2beec)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Verify Contracts via Dashboard - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/contract-verification/dashboard#content-area)

**Works on:** public networks (mainnets and testnets). To verify a contract on a Virtual Environment, see [Deploy and verify contracts](https://docs.tenderly.co/virtual-environments/develop/deploy-contracts)
.

Verify smart contracts from your browser in the Tenderly Dashboard. This is the fastest path when you’re not using Hardhat or Foundry; if you are, the [Hardhat](https://docs.tenderly.co/contract-verification/hardhat)
 or [Foundry](https://docs.tenderly.co/contract-verification/foundry)
 workflows automate this.

[​](https://docs.tenderly.co/contract-verification/dashboard#prerequisites)

Prerequisites
--------------------------------------------------------------------------------------------

To verify a contract, you need to provide:

*   **The source code**
*   **The exact compiler settings** used to compile the deployed version

You can upload the source code in several ways through the Dashboard:

*   **JSON Upload**: paste the JSON metadata generated by the Solidity compiler.
*   **ABI Upload**: paste the contract ABI.
*   **Contract Source Upload**: paste source code directly, upload a single source file, or upload an entire project directory. The directory option works best for contracts that import other contracts.

[​](https://docs.tenderly.co/contract-verification/dashboard#public-and-private-verification)

Public and private verification
--------------------------------------------------------------------------------------------------------------------------------

When verifying a contract, you choose between two visibility modes:

*   **Public**: the contract source is visible to anyone using Tenderly.
*   **Private**: the contract source is only visible inside the project you verified it in.

The **Verification** column on the Contracts list shows a contract’s current status: `Unverified`, `Public`, or `Private`.

[​](https://docs.tenderly.co/contract-verification/dashboard#dashboard-contract-verification-guide)

Dashboard contract verification guide
--------------------------------------------------------------------------------------------------------------------------------------------

After you’ve [added an unverified contract](https://docs.tenderly.co/developer-explorer/contracts)
 to a Tenderly project, here are the steps to verify it using the Dashboard.

1

Find the unverified contract

Open the contract’s page. An unverified contract shows a banner with a **Verify Contract** button.![Unverified contract banner with Verify Contract button](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/verify-button-context.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=f63d4b92fc914de54ffa4f603eeb26f9)

2

Choose visibility

Select **Public** or **Private**. Private is selected by default, and scopes the verified source to the current project.![Verify Contract visibility step](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/select-contract-visibility.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=8c451a583998665f82adc087fba7810f)

3

Choose the upload method

Pick one of:

*   **JSON Upload**
*   **ABI Upload**
*   **Contract Source Upload**, which opens a submenu: **Paste Source Code**, **Upload Source File**, or **Upload Project Directory**. ![Verify Contract source code upload method choice](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/upload-method-choice.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=57c6978f24e7fd6e5e4f1417e558b648) ![Contract Source Upload submenu](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/upload-method-submenu.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=a56a9b79641813f05b5c215aa705de45)

If you paste source directly, give the file a name and paste the contract source into the editor.![Paste source code screen](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/paste-source-code-screen.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=c19036952b457c3e4662588c486a53f0)

4

Select the contract

If the upload contains several contracts, pick the one matching the address shown in the previous step. If any imports are missing, the Dashboard prompts you to add them before continuing.![Choose a Deployed Contract step](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/select-deployed-contract.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=a7bfef85d83285fea8f8e6853a7a476c)

5

Set the compiler settings

Fill in the compiler version, optimizer settings (enabled / runs), EVM version, ViaIR, and library address pairs if your contract uses linked libraries. Any mismatch with the deployed bytecode will fail verification.![Compiler Settings step filled in](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/compiler-settings.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=55cdf882ebed51f7916d2559ccd7f800)

6

Finish

Click **Finish** to submit. The contract’s verification status and info panel update immediately.![Contract page after successful private verification](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/verification-success.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=db60043d18efea878b7f59bcf8260fc8)

[​](https://docs.tenderly.co/contract-verification/dashboard#how-to-verify-smart-contracts-in-bulk)

How to verify smart contracts in bulk
--------------------------------------------------------------------------------------------------------------------------------------------

If you have several unverified contracts in your project, click **Verify All Contracts** on the Contracts list. This opens the **Verify multiple contracts** dialog, listing every unverified contract with a **Make Private** toggle and an **Add source** button per row. ![Verify multiple contracts dialog](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/contract-verification/verify-all-contracts-modal.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=994ae13c3c8b0e6dd7f017fdd74142ea) Click **Add source** next to each contract and supply the upload, compiler settings, and visibility as in the [single-contract flow](https://docs.tenderly.co/contract-verification/dashboard#dashboard-contract-verification-guide)
 above. The bottom **Verify** button stays disabled until every row has a source, then submits all of them at once.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Gas Profiler - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/gas-profiler#content-area)

Gas Profiler gives you a breakdown of gas consumption, revealing how each function within a contract uses gas during execution. When combined with Debugger and Simulator, Gas Profiler makes up the core of the Developer Explorer. ![Gas profiler](https://mintcdn.com/tenderly/8ACOAR8iGyQOJzee/images/developer-explorer/profiler/gas-profiler-2.webp?w=2500&fit=max&auto=format&n=8ACOAR8iGyQOJzee&q=85&s=863fe268ffe8bd80775c5710a1818a6a)

[​](https://docs.tenderly.co/debugger/gas-profiler#getting-started-with-gas-profiler)

Getting started with Gas Profiler
--------------------------------------------------------------------------------------------------------------------------

1.  Open any transaction from the transaction listing page. Try this [example transaction](https://dashboard.tenderly.co/tx/1/0x1696cfc031695003b8a58f0379c7f111b34c7612a67681354dc57cb5853c5c63/gas-usage)
    .
2.  Navigate to **Gas Profiler** in the top menu to access an interactive flame chart with detailed gas usage breakdowns for each called function, including internal transactions.
3.  Click on any function to reveal a detailed view of its gas usage.
4.  For deeper insights, [open the transaction in Debugger](https://docs.tenderly.co/debugger/overview)
     to pinpoint the exact line of code in the Solidity file responsible for execution.

![Gas profiler](https://mintcdn.com/tenderly/8ACOAR8iGyQOJzee/images/developer-explorer/profiler/profiler-debugger.webp?w=2500&fit=max&auto=format&n=8ACOAR8iGyQOJzee&q=85&s=a02fcad3bd96e544287547edca70f90a)

### 

[​](https://docs.tenderly.co/debugger/gas-profiler#optimizing-gas-usage)

Optimizing gas usage

1.  Clicking on a function call in the flame chart displays detailed gas usage information in the lower pane.
2.  If you suspect a function requires gas optimization, click the **View in Debugger** button to dive into the code and optimize it to reduce gas usage.
3.  To verify that the changes help reduce gas usage, you can simulate the same transaction with the changed code and compare the gas profiling result.

#### 

[​](https://docs.tenderly.co/debugger/gas-profiler#total-gas-vs-actual-gas)

Total gas vs actual gas

**Total Gas** represents the overall gas cost of execution, encompassing the sum of gas costs associated with all invoked opcodes. **Actual Gas** denotes the net gas cost of the execution. When multiplied by the `gas_price`, it provides the exact amount you would pay for this execution in wei. The formula for calculating Actual Gas: `actual_gas_used = total_gas - gas_refund`. Blockchain users receive rewards for clearing up storage, manifested in the form of [gas refunds](https://github.com/wolflo/evm-opcodes/blob/main/gas.md#a0-3-gas-refunds)
 for `SSTORE` invocations that effectively “delete” existing stored data. These gas refunds are subtracted from the Total Gas, resulting in the Actual Gas used.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Transaction Listing - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/developer-explorer/transaction-listing#content-area)

Once you add a contract or wallet from any supported network, all the transactions coming from those assets will be displayed in the Dashboard. This makes it easy to keep track of everything in one place. You can also use filters to sort and find the transactions that are most important to you, which can be helpful both during development and monitoring. [Watch on Loom →](https://www.loom.com/share/ec9c8aac4ca24bb19226b6dd96606f97?sid=07229573-c019-42d8-8a6c-8a89acdefbb3)
 To see all your project’s transactions, go to the **Transactions** page. Here, you can apply filters and sort transactions to hone in on the information most relevant to you. Click on the **Filters** button to access the filtering and sorting options. ![Transaction Filtering Overview](https://mintcdn.com/tenderly/8ACOAR8iGyQOJzee/images/developer-explorer/transactions/transaction-filtering-main.webp?w=2500&fit=max&auto=format&n=8ACOAR8iGyQOJzee&q=85&s=2173927132f4505cddc8b0065318dcd7) Transactions can be filtered by their:

*   **Status** (success, [pending](https://docs.tenderly.co/developer-explorer/inspect-transaction/overview#mempool-pending-transactions)
    , failed)
*   **Type** (internal and direct)
*   **Contract addresses** involved
*   **Function** called
*   **Network** (98 networks supported)
*   **Date** or date range
*   **Tag**, matching any [tag you’ve added](https://docs.tenderly.co/developer-explorer/wallets#adding-tags-to-wallets)
     to a contract or wallet

![Detailed Transaction Filtering](https://mintcdn.com/tenderly/8ACOAR8iGyQOJzee/images/developer-explorer/transactions/transaction-filtering.webp?w=2500&fit=max&auto=format&n=8ACOAR8iGyQOJzee&q=85&s=099553b6a0072e2b816d68e40c5957d2)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# DeFi Modules - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/defi-modules/overview#content-area)

DeFi Modules are protocol-specific UI surfaces that Tenderly renders when an address or transaction is recognized as belonging to a supported protocol. Instead of displaying raw ABI calls, hex-encoded event logs, and storage slots, Tenderly resolves the protocol context and presents the data using that protocol’s own terminology, structure, and metrics. Recognition is automatic and requires no configuration. When you navigate to a supported address, the module activates and the protocol-native view replaces the generic contract view. The underlying raw data remains accessible on the same page. ![Morpho vault page showing the protocol badge, total deposits, liquidity, market exposure, net APY, pending governance, and classified transactions](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/morpho-vault-overview.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=b26bdbe59826c97c11b1c9c80665a57c)

* * *

[​](https://docs.tenderly.co/defi-modules/overview#surfaces)

Surfaces
------------------------------------------------------------------------

Each supported protocol activates up to three surfaces. All three surfaces are driven by the same underlying module definition, so data is consistent across views.

### 

[​](https://docs.tenderly.co/defi-modules/overview#protocol-overview)

Protocol overview

A dedicated page rendered for each recognized pool, vault, or reserve. The page includes a protocol badge identifying the contract, a set of protocol-native metrics in the header (such as total supplied, borrow APY, utilization, and reserve factor), a time-series chart for the primary metric, and a list of related entities. Governance state and pending proposals are surfaced inline where applicable. The Protocol overview tab is available alongside the standard Transactions, Relationships, and Alerts tabs on any recognized address page. ![Aave V3 USDC reserve showing total supplied, supply and borrow APY, reserve factor, the supply APY chart, and classified transactions](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/aave-pool-overview.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=aab378777e8b56095d918a515ef6d950)

### 

[​](https://docs.tenderly.co/defi-modules/overview#wallet-360)

Wallet 360

A wallet-scoped view of positions held in a supported protocol. Accessed via the Wallet 360 tab on a protocol page, it shows the wallet’s balance, deposits, and borrows over time as a chart, and lists each open position with its token, deposit amount, current APY, health factor after the last transaction, earned interest, collateral status, and claimable rewards. To view Wallet 360 data, use the Impersonate wallet function to select or enter a wallet address. Wallet 360 data reflects the on-chain state of that wallet’s positions within the current protocol. Coverage varies by protocol: Aave V3 shows deposit and borrow positions with the health factor after the last transaction, Uniswap V3 shows directly held LP positions via the NFT Position Manager, and Morpho shows borrow and lend positions. ![Wallet 360 tab on the Aave V3 USDC reserve showing balance, deposits, borrows chart, and open positions table](https://mintcdn.com/tenderly/zoe81uybP1hGOl1w/images/defi-modules/wallet-360.webp?w=2500&fit=max&auto=format&n=zoe81uybP1hGOl1w&q=85&s=36c14c5d527aab9cb8e9ca6721dde6a6)

### 

[​](https://docs.tenderly.co/defi-modules/overview#transaction-classification)

Transaction classification

Transactions involving a supported protocol are classified and labeled in the transaction list and transaction detail view. Each transaction is assigned a human-readable action type (for example: Supply, Borrow, Repay, and Withdraw on Aave, Deposit and Withdraw on Morpho, or Buy and Sell labels for Uniswap swaps) and attributed to the correct protocol. Multi-step transactions that touch multiple contracts are grouped under a single classified action. Raw decoded event logs remain visible beneath the classification. ![Recent activity on the Uniswap V3 WBTC/ETH pool with each transaction classified as Buy WBTC or Sell WBTC, alongside the wallet, USD value, and token amounts](https://mintcdn.com/tenderly/ByKNsKKrGuJbu3zy/images/defi-modules/uniswap-pool-transactions.webp?w=2500&fit=max&auto=format&n=ByKNsKKrGuJbu3zy&q=85&s=21a398362e1f8375a799ad20f2d67a98)

* * *

[​](https://docs.tenderly.co/defi-modules/overview#supported-protocols)

Supported protocols
----------------------------------------------------------------------------------------------

Each protocol page documents the module in detail: the header metrics, the charts, and what each tab renders.

Aave V3
-------

Reserve pages with supply and borrow metrics, APY charts, classified transactions, and Allocation, Performance, and Risk views.

Uniswap V3
----------

Pool pages with price, volume, and liquidity charts, classified Buy and Sell swaps, and market depth metrics.

Morpho
------

Vault pages with deposit and share price charts, market allocation, timelocks, and user distribution.

* * *

[​](https://docs.tenderly.co/defi-modules/overview#virtual-environments)

Virtual Environments
------------------------------------------------------------------------------------------------

DeFi Modules are also active on [Virtual Environments](https://docs.tenderly.co/virtual-environments/overview)
. A Virtual Environment forked from a network where a protocol is supported inherits the live protocol state, and the same module surfaces are available within the Virtual Environment.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# War Room Aid Kit - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/war-room-aid-kit#content-area)

Diagnosing Web3 errors is complex and hard, that’s why development teams have adopted War Rooms in response to high-stakes errors and hacks. With Tenderly you can now adopt a War Room procedure and be ready when the problem arises. **Detect issues faster** If the number of contracts in the transaction is greater than 30 then [**Call Trace**](https://docs.tenderly.co/debugger/overview)
 will be automatically triggered. You can switch it yourself if you’re only interested in seeing external calls that are usually crucial for the attack. Use [**Expression Evaluation**](https://docs.tenderly.co/debugger/evaluate-expression)
 to better understand the whole context of the transaction and simplify debugging process. **Collaborate and prioritize** With the new annotation system, you can leave comments on the exact line of code you think caused the issue. Annotations can be used to make team collaboration more efficient or to leave a note for yourself so you don’t forget it later. You can also set a priority for traces you want inspected first.

### 

[​](https://docs.tenderly.co/debugger/war-room-aid-kit#tenderly-in-war-rooms)

Tenderly in War Rooms

Get familiar with the features that can help you understand and debug your code faster and collaborate with your team:

Tenderly War Rooms: The Aid Kit You Need in Time-Sensitive Scenarios
--------------------------------------------------------------------

### 

[​](https://docs.tenderly.co/debugger/war-room-aid-kit#anatomy-of-a-good-emergency-procedure)

Anatomy of a Good Emergency Procedure

We tapped into Yearn Finance’s best-in-class procedures to give you an overview of the War Room best practice:

The Anatomy of a Good Emergency Procedure \[Yearn Finance Case Study\]
----------------------------------------------------------------------

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Evaluate Expressions with Advanced Debugger - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/evaluate-expression#content-area)

Evaluate Expression is a tool in [Debugger](https://docs.tenderly.co/debugger/overview)
 that allows you to evaluate expressions in the execution trace. You can assess complex expressions in smart contracts, including dynamic arrays, mappings, state variables, functions, and both global and local variables. Learn more about [how Evaluate works](https://blog.tenderly.co/how-use-evaluate-expression-speed-debugging)
. To access the Evaluate feature, click on any transaction, then go to the **Debugger**, and click on the **Evaluate** button. ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.33.34.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=eed0182751877939f3d216c77f2ae7e8) ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.34.54.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=551647abd138579a11db3c90e5416e58) ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.36.18.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=87492e852de8e629e24f2467365ec156) The Evaluate feature currently supports Solidity contracts. Choose any expression you want to evaluate, paste it into the box and hit the **Evaluate** button: ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.44.01.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=d43da54e995f5eb0d7f4555c81051a93) ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.44.36.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=782ed4490e1014c8e179c61c38157036) ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.44.57.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=4bc6ca2c901c0473d526a83f224b14f5) This works for both simple and complex expressions: ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.45.55.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=81e5079310aa45783b7959d8ad8041b0) ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-04-14%20at%2012.47.27.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=6f1c32498865349881ff538aa2020806) Learn more about other [Debugger features](https://docs.tenderly.co/debugger/overview#stack-traces)
 and [searching the call trace](https://docs.tenderly.co/developer-explorer/inspect-transaction/overview#search-the-call-trace)
.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Commenting & Prioritizing Traces - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/commenting#content-area)

Collaboration can be complex and time-consuming when you go through various contracts and Execution Traces ([**Function Trace and Call Trace**](https://docs.tenderly.co/debugger/execution-overview)
). That is why you can comment on any trace, as well as set priorities. Click the speech-bubble icon next to a trace node in the execution tree to open its comment panel on the right side of the Debugger. The panel header shows the number of comments on that trace (for example, “0 comments on `exactInputSingle`”), and you can post a reply from the box at the bottom of the panel. ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-01-17%20at%2015.14.56.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=4743b3315a7d33ef97a12cdf3a06a9ea) When you select a trace, you can clearly prioritize it. In the top right of the trace window you can see the option _**Set priority**_ right next to [_View in Debugger_](https://docs.tenderly.co/debugger/overview)
 button - clicking on it opens a dropdown from which you can select the priority you want for that particular trace and it will stay marked for all users that have access to the project until manually changed. Selecting _None_ for the priority of a trace removes the markings. Lastly, clicking on the three dots next to _Set priority_ opens up a dropdown where you can [view the contract source](https://docs.tenderly.co/simulator-ui/editing-contract-source)
. ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-01-17%20at%2015.16.29.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=a56965b19a1e08332de6673e92a9ea67) All the comment and priority features persist through both Transaction Overview and Debugger views in your dashboard. ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-01-17%20at%2015.21.04.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=63bf7d9cbf783fe5d9f699b3c44f68f3) You can delete your own comments from the comment panel. ![](https://mintcdn.com/tenderly/Aq90dolhrsdO4Ket/images/Screenshot%202022-01-19%20at%2009.08.04.webp?w=2500&fit=max&auto=format&n=Aq90dolhrsdO4Ket&q=85&s=6d1928cfaace91adf399e45bc5ab9f07)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Smart Contract Verification - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/contract-verification/overview#content-area)

Contract verification submits the source code of a deployed contract so Tenderly can match it against the on-chain bytecode. Once verified, Tenderly can decode that contract’s transactions, events, and state changes in:

*   **Decoded transactions**: call traces, events, state changes, and gas usage become human-readable.
*   **Debugger**: step through execution against the original Solidity, set priorities, and comment on traces.
*   **Gas profiler**: line-level gas attribution against the source.
*   **Sharing**: share verified contracts with collaborators and auditors.

Without verification you’ll see raw bytecode in every Tenderly tool that touches that contract.

[​](https://docs.tenderly.co/contract-verification/overview#pick-a-method)

Pick a method
-------------------------------------------------------------------------------------------

For verification on **public networks** (mainnets and testnets), pick the guide that matches your tooling:

*   [Dashboard](https://docs.tenderly.co/contract-verification/dashboard)
    : browser-only verification from the Tenderly Dashboard.
*   [Foundry](https://docs.tenderly.co/contract-verification/foundry)
    : `forge verify-contract` and deploy-and-verify with `forge create` / `forge script`.
*   [Hardhat](https://docs.tenderly.co/contract-verification/hardhat)
    : the `@tenderly/hardhat-tenderly` plugin, automatic or manual.
*   [Hardhat (proxy contracts)](https://docs.tenderly.co/contract-verification/hardhat-proxy)
    : UUPS, Transparent, and Beacon proxies.

To verify contracts on a **Virtual Environment**, see [Deploy and verify contracts](https://docs.tenderly.co/virtual-environments/develop/deploy-contracts)
 and [Verify proxy contracts with Foundry](https://docs.tenderly.co/virtual-environments/develop/verify-proxy-contracts)
 under Virtual Environments.

[​](https://docs.tenderly.co/contract-verification/overview#public-vs-private-visibility)

Public vs private visibility
-------------------------------------------------------------------------------------------------------------------------

On **public networks** you choose between two visibility modes:

*   **Public verification.** Source is visible to everyone on Tenderly and propagated to public verification registries.
*   **Private verification.** Source is visible only inside your Tenderly project and organization.

On **Virtual Environments** verifications are always scoped to your project and organization. There is no public mode; see [Deploy and verify contracts](https://docs.tenderly.co/virtual-environments/develop/deploy-contracts)
.

| Who can see the verified source | Public verification (public network) | Private verification (public network) | Virtual Environment |
| --- | --- | --- | --- |
| All Tenderly users | ✓   |     |     |
| Project collaborators | ✓   | ✓   | ✓   |
| Organization members | ✓   | ✓   | ✓   |

How to switch to private mode depends on the method:

*   **Hardhat**: set `tenderly.privateVerification: true` in `hardhat.config.ts`. See [Hardhat setup](https://docs.tenderly.co/contract-verification/hardhat#configure-authentication-and-verification-visibility)
    .
*   **Foundry**: append `/public` to the verifier URL to verify publicly, omit it to verify privately. See [Foundry verifier URL](https://docs.tenderly.co/contract-verification/foundry#verifier-url)
    .
*   **Dashboard**: toggle **Make Private** in the verification dialog. See [Dashboard verification](https://docs.tenderly.co/contract-verification/dashboard#public-and-private-verification)
    .

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Fund Flow - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#content-area)

The **Fund Flow** tab on any transaction page renders all token transfers as an interactive directed graph. You can follow the entire flow of token transfers within a transaction, from the first to the last step. Inspect which addresses (represented as nodes) were involved, apply filters to focus on an exact token path, and jump straight to a function call from the graph. Open a transaction in the [Tenderly Explorer](https://docs.tenderly.co/developer-explorer/overview)
 and click the **Fund Flow** tab to see the graph.  Fund Flow supports all standard transfer types:

| Transfer type | Source |
| --- | --- |
| ERC-20 | `Transfer(from, to, value)` event |
| ERC-721 (NFTs) | `Transfer(from, to, tokenId)` event |
| ERC-1155 | `TransferSingle` / `TransferBatch` events |
| Native ETH (external) | Transaction value field |
| Native ETH (internal) | Internal `CALL` with value > 0 |
| WETH wrap/unwrap | `Deposit` / `Withdrawal` events |

Fund Flow displays the same data as the [Tokens Transferred](https://docs.tenderly.co/developer-explorer/inspect-transaction/overview#tokens-transferred)
 list, rendered as a graph. Use it when a transaction involves many intermediary hops and a visual layout makes the flow easier to follow.

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#timeline-navigation)

Timeline navigation
-------------------------------------------------------------------------------------------------------------------------

The timeline bar at the bottom of the graph lets you step through transfers in execution order. Each step highlights the active transfer edge and the two addresses involved, building up a visual history as you advance.

*   **Right arrow**: advance to the next transfer
*   **Left arrow**: go back to the previous transfer
*   Past transfers remain visible at reduced opacity, giving you the “story so far”

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#address-details-and-net-positions)

Address details and net positions
-----------------------------------------------------------------------------------------------------------------------------------------------------

Click any node to open a side panel with:

*   **Address identity**: type (EOA, contract, proxy), verification status, labels, and ENS name
*   **Transfers**: every inflow and outflow involving that address within this transaction, each with its sequence number and counterparty
*   **Net position**: the total balance change per token, converted to USD, so you can instantly see the balance of a particular address at the end of the transaction.

### 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#label-and-color-code-addresses)

Label and color-code addresses

You can assign custom labels and colors to any address directly from the graph. Labels persist across your project workspace, so key contracts are recognizable in every transaction you inspect. 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#jump-to-execution-trace)

Jump to execution trace
---------------------------------------------------------------------------------------------------------------------------------

Click any transfer edge and select **Jump to Trace** to open the exact function call in the [execution trace](https://docs.tenderly.co/developer-explorer/inspect-transaction/overview#decoded-call-trace)
. The trace opens within the graph context so you can inspect the low-level call right away. 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#search)

Search
-----------------------------------------------------------------------------------------------

Use the search bar to find any element in the graph by:

*   Address (full or partial)
*   Contract name or label
*   Token symbol
*   Transfer amount

Matches are highlighted in place and the graph auto-pans to center the result. 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#filtering)

Filtering
-----------------------------------------------------------------------------------------------------

Apply filters to isolate specific paths throughout the transaction:

| Filter | Options |
| --- | --- |
| **Token** | Select specific tokens or token types (ERC-20, ERC-721, native) |
| **Address** | Filter by specific address or address type (EOA, contract) |
| **Transfer type** | Mint, burn, or transfer |

### 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#quick-filter-from-the-graph)

Quick filter from the graph

Each transfer edge in the graph has an inline filter icon. Click it to instantly scope the view to that transfer’s token and path, without opening the filter panel. This is the fastest way to isolate a specific token flow while exploring the graph. When filters are active, the timeline applies to the scoped view, letting you trace specific addresses, tokens, and transfer types. 

[​](https://docs.tenderly.co/developer-explorer/inspect-transaction/fund-flow#when-to-use-fund-flow)

When to use Fund Flow
-----------------------------------------------------------------------------------------------------------------------------

Fund Flow is most useful for transactions with complex token routing:

*   **DEX swaps** routed through multiple pools or aggregators
*   **Flash loans** where borrowed assets flow through several contracts before repayment
*   **Arbitrage and MEV** transactions where spotting circular flows or sandwich patterns is critical
*   **Multi-step DeFi** operations (e.g., borrow, swap, provide liquidity in a single transaction)
*   **Security investigations** where you need to quickly identify which addresses gained or lost assets

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Claude और AI assistants के लिए Tenderly MCP Server - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/hi/ai-tools/overview#content-area)

Tenderly MCP Server AI assistants को Tenderly तक सीधी पहुँच देता है, Virtual Environments बनाना, transactions simulate करना, execution ट्रेस करना, contracts का निरीक्षण करना, और बहुत कुछ। अपने पूरे smart contract विकास workflow को चलाने के लिए Claude में प्राकृतिक भाषा का उपयोग करें।

MCP Server paid plan पर उपलब्ध है। अपने account के लिए इसे सक्षम करने के लिए, [हमारी sales team से संपर्क करें](https://tenderly.co/contact-us)
। आपको एक [Tenderly account](https://dashboard.tenderly.co/register)
 और कम से कम एक project की भी आवश्यकता होगी।

[​](https://docs.tenderly.co/hi/ai-tools/overview#%E0%A4%B6%E0%A5%81%E0%A4%B0%E0%A5%81%E0%A4%86%E0%A4%A4-%E0%A4%95%E0%A4%B0%E0%A5%87%E0%A4%82)

शुरुआत करें
-------------------------------------------------------------------------------------------------------------------------------------------------------------

Quickstart
----------

Tools Reference
---------------

उदाहरण
------

[​](https://docs.tenderly.co/hi/ai-tools/overview#mcp-%E0%A4%95%E0%A5%8D%E0%A4%AF%E0%A4%BE-%E0%A4%B9%E0%A5%88)

MCP क्या है?
------------------------------------------------------------------------------------------------------------------------------

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/)
 Anthropic द्वारा एक open standard है जो AI मॉडल को बाहरी टूल्स और डेटा स्रोतों से जुड़ने देता है। RPC responses को copy-paste करने या curl commands लिखने के बजाय, Claude सीधे Tenderly टूल्स को call कर सकता है, लाइव blockchain डेटा, transaction simulation, debugging, और Virtual Environment प्रबंधन सब कुछ बातचीत के भीतर होता है।

[​](https://docs.tenderly.co/hi/ai-tools/overview#%E0%A4%95%E0%A5%8D%E0%A4%B7%E0%A4%AE%E0%A4%A4%E0%A4%BE%E0%A4%8F%E0%A4%81)

क्षमताएँ
---------------------------------------------------------------------------------------------------------------------------------------

MCP Server सात क्षेत्रों में **59 टूल** प्रदान करता है:

*   **Virtual Environments**: private blockchain परिवेश बनाएँ, fork करें, delete करें, और प्रबंधित करें। एक Virtual Environment को active सेट करें और उसके बाद के सभी टूल स्वचालित रूप से उस पर काम करते हैं। accounts fund करें, ERC-20 balances सेट करें, storage slots में लिखें, impersonated transactions भेजें, read-only contract calls करें, blocks mine करें, समय आगे बढ़ाएँ, और branching test scenarios के लिए snapshots save/restore करें।
*   **Transaction Simulation**: gas खर्च किए बिना किसी भी समर्थित EVM नेटवर्क पर किसी भी transaction को simulate करें। decoded call traces, events, state changes, asset transfers, और balance diffs प्राप्त करें।
*   **Transaction Tracing**: पूर्ण execution विवरण के साथ on-chain और Virtual Environment transactions को ट्रेस करें। call trees, gas breakdown, state diffs, और EIP-2930 access lists का निरीक्षण करें।
*   **Advanced Trace Navigation**: सैकड़ों या हजारों internal calls वाले जटिल transactions को नेविगेट करने के लिए 16 टूल्स। इसमें trace size निरीक्षण, skeleton views, subtree drilling, failure detection, error path tracing, और fund flow विश्लेषण शामिल है।
*   **Contract Inspection**: किसी भी address के लिए contract metadata प्राप्त करें: नाम, ABI, compiler version, token standards, और creation जानकारी।
*   **Network Discovery**: Tenderly द्वारा समर्थित सभी 100+ EVM नेटवर्क सूचीबद्ध करें।
*   **Project Management**: projects सूचीबद्ध करें और active project संदर्भ सेट करें।

हर टूल के विवरण के लिए पूर्ण [Tools Reference](https://docs.tenderly.co/ai-tools/tools)
 देखें।

[​](https://docs.tenderly.co/hi/ai-tools/overview#%E0%A4%B8%E0%A4%AE%E0%A4%B0%E0%A5%8D%E0%A4%A5%E0%A4%BF%E0%A4%A4-clients)

समर्थित clients
---------------------------------------------------------------------------------------------------------------------------------------------

Tenderly MCP Server किसी भी MCP-संगत client के साथ काम करता है:

*   **Claude Code**: एक कमांड के साथ CLI के माध्यम से जोड़ें
*   **Claude.ai**: Settings → Connectors के माध्यम से जुड़ें
*   **Claude Desktop**: Settings → Connectors के माध्यम से जुड़ें
*   **Cursor/VS Code**: अपने MCP config में server URL जोड़ें

प्रत्येक client के लिए सेटअप निर्देशों के लिए [Quickstart](https://docs.tenderly.co/ai-tools/quickstart)
 देखें।

[​](https://docs.tenderly.co/hi/ai-tools/overview#authentication)

Authentication
-----------------------------------------------------------------------------------

MCP Server [WorkOS](https://workos.com/)
 के माध्यम से OAuth 2.0 का उपयोग करता है। जब आप Claude से कनेक्ट करते हैं, तो आप log in और access authorize करने के लिए Tenderly पर redirect होंगे। Claude केवल आपकी अनुमतियों के दायरे में क्रियाएँ कर सकता है। Claude में connector को disconnect करके किसी भी समय access revoke करें।

वाज़ दिस पेज हेल्पफुल

यसनो

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# How to Use Tenderly Debugger - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/overview#content-area)

The Tenderly Debugger steps through an EVM transaction’s execution, one call and source line at a time, exposing the execution trace, stack, contract state, and the exact point where a transaction reverts. Use it to find why a transaction failed, inspect contract state at any step, and replay a transaction against verified Solidity source. Watch this quick video to learn the basics of using Debugger and follow the quickstart below for a detailed feature walkthrough. [Watch on Loom →](https://www.loom.com/share/09413e8a867f4ddeaa41a5080d771895?sid=b8f60cda-fcb8-401b-ba9a-8bb69630fe9a)

[​](https://docs.tenderly.co/debugger/overview#debugger-quickstart)

Debugger quickstart
------------------------------------------------------------------------------------------

To use the Debugger, you need to start from a specific transaction. Try this [example transaction](https://dashboard.tenderly.co/tx/0x1696cfc031695003b8a58f0379c7f111b34c7612a67681354dc57cb5853c5c63/debugger?trace=0.2.6.21.1&pk_vid=4405d1610803d9751776942168287f02)
.

1.  Go to the **Transactions** tab on the left side or search for a transaction hash in the top Explorer bar.
2.  Click the **Debugger** button located at the top right.

The Debugger interface is comprised of four main panels: ![Debugger panels](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/developer-explorer/debugger/debugger-panels-2.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=c558141733a26383a52d1a007714f04e)

*   **Execution trace** (top left): Displays the sequence of calls made during the transaction.
*   **Smart contract source code** (top right): Shows the code of the contract being interacted with.
*   **Stack trace** (bottom left): Lists the methods called leading up to the current function.
*   **Call information** (bottom right): Provides detailed info about the current call.

[​](https://docs.tenderly.co/debugger/overview#execution-trace)

Execution trace
----------------------------------------------------------------------------------

The **Execution Trace** section lets you see every call made during a transaction’s life cycle. A handy toggle allows you to filter the view between the full trace or just the `CALL`s and `DELEGATECALL`s. You can also leave comments directly on any part of the trace, useful for collaboration or personal notes. ![Debugger panels](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/developer-explorer/debugger/comment-execution-trace.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=2385e13c8eaad7c69a6d740c210b0afb)

[​](https://docs.tenderly.co/debugger/overview#stack-trace)

Stack trace
--------------------------------------------------------------------------

The **Stack Trace** offers a look at the methods that have been invoked leading up to the active function call, giving you a clearer picture of the transaction’s flow.

[​](https://docs.tenderly.co/debugger/overview#decoding-call-information)

Decoding call information
------------------------------------------------------------------------------------------------------

Here, you get decoded details about the current call in the transaction’s execution trace in JSON format. This includes:

*   Invoked function’s name
*   Opcodes (`JUMP`, `CALL`, `DELEGATECALL`, `STATICCALL`, `CREATE2`, `CREATE`, `REVERT`, `JUMPDEST`)
*   Contract and caller addresses, plus the caller’s balance
*   Decoded inputs and outputs
*   Gas usage stats, showing total gas used, gas consumed by the current function, and remaining gas

[​](https://docs.tenderly.co/debugger/overview#navigating-through-the-call-trace)

Navigating through the call trace
----------------------------------------------------------------------------------------------------------------------

Jumping through the call trace and code lines is straightforward with the Debugger’s navigation buttons. **Next/Previous** moves you through the call trace, while **Step Up** and **Step Over** help you navigate the stack trace and call levels. ![Debugger panels](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/developer-explorer/debugger/debugger-skip-call-trace.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=5d5575b67681183bfab4428366e64d42)

[​](https://docs.tenderly.co/debugger/overview#evaluating-expressions)

Evaluating expressions
------------------------------------------------------------------------------------------------

The **Evaluate** feature allows you to test out expressions directly within the Debugger. This is perfect for checking global variables, contract variables, function arguments, and local variables. ![Eval modal](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/developer-explorer/debugger/debugger-evaluate.webp?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=ce4e159271ccce6c6fc3cdad402a5d82) The current version of **Evaluate** supports expressions in the form of arrays and structs. Tuples are not supported so they can’t be evaluated. ![Debugger + expressions visible for Eval](https://mintcdn.com/tenderly/czz1ot21Icudd1fI/images/developer-explorer/debugger-1.png?w=2500&fit=max&auto=format&n=czz1ot21Icudd1fI&q=85&s=84bf987772842ccc3f511d5beaadb876)

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Investigating a Failed Transaction - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/debugger/guides/failed-transaction#content-area)

In this guide, we’ll investigate the root cause of transaction failure and verify the fix. We’ll look into a [Uniswap transaction](https://www.tdly.co/tx/1/0xbe082dcc8ae59868f5b2330173902bb88c6643b5c2fdf0d8a9f43d03dbca0c36)
. This transaction attempts to `swapExactTokensForTokens`.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Simulation Mode in the Explorer - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/developer-explorer/simulation-mode#content-area)

Simulation Mode is a persistent “act-as-this-wallet” context. When it is active, Explorer pages render and simulate as the impersonated wallet: contract Read/Write pages auto-fill the `From` address, wallet pages expose one-click impersonation, and transaction pages let you re-simulate as that wallet. This page covers the Explorer surfaces wired into Simulation Mode. For the session model, balance overrides, state settings, and the Sim Mode panel itself, see the full [Simulation Mode](https://docs.tenderly.co/simulator-ui/simulation-mode)
 documentation.

[​](https://docs.tenderly.co/developer-explorer/simulation-mode#entering-simulation-mode-from-the-explorer)

Entering Simulation Mode from the Explorer
---------------------------------------------------------------------------------------------------------------------------------------------------------

There are two entry points:

*   **Top bar**: click **Enter Simulation Mode** and pick a wallet and network. The button is available on every Explorer page.
*   **Wallet detail pages**: an **Impersonate** button sits between Create Alert and Simulate. It activates Simulation Mode pre-filled with that wallet, with no picker step.

Once active, the top-bar button is replaced with a `SIMULATING` pill showing the wallet’s identity icon, abbreviated address, and total USD balance. The context follows you across pages until you exit.

[​](https://docs.tenderly.co/developer-explorer/simulation-mode#explorer-surfaces-wired-into-simulation-mode)

Explorer surfaces wired into Simulation Mode
-------------------------------------------------------------------------------------------------------------------------------------------------------------

| Surface | Behavior when Sim Mode is active |
| --- | --- |
| **Contract Read/Write pages** | A purple banner indicates Sim Mode is active. The Write button is hidden and **Simulate** becomes the primary action. The `From` field auto-fills with the impersonated wallet. |
| **Transaction detail** | The Re-Simulate dropdown gains a **Re-simulate as \[wallet\]** option, so you can replay any transaction as the impersonated wallet. |
| **Wallet detail pages** | The **Impersonate** button activates Sim Mode for that wallet directly. |

If you open a page on a network different from your active session, a banner offers a one-click **Switch Sim Mode to \[network\]**. Read and Write actions are disabled until you switch.

[​](https://docs.tenderly.co/developer-explorer/simulation-mode#relation-to-the-simulator)

Relation to the Simulator
-----------------------------------------------------------------------------------------------------------------------

Simulation Mode and the [Simulator](https://docs.tenderly.co/simulator-ui/overview)
 are complementary:

*   **Simulation Mode** is a session: simulations accumulate, each run sees the state the previous ones produced, and the wallet context persists across Explorer pages.
*   The **Simulator** is where you build and run individual simulations and multi-step bundles. With Sim Mode active, the Simulator pre-fills the sender as the impersonated wallet and successful runs append to the session log.

[​](https://docs.tenderly.co/developer-explorer/simulation-mode#see-also)

See also
-------------------------------------------------------------------------------------

*   [Simulation Mode](https://docs.tenderly.co/simulator-ui/simulation-mode)
    : the full session model, Tokens tab, balance overrides, and state settings.
*   [Simulator UI](https://docs.tenderly.co/simulator-ui/overview)
    : single simulations and bundles.
*   [Wallets in the Explorer](https://docs.tenderly.co/developer-explorer/wallets)
    : adding and managing wallets.

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---

# Developer Explorer - Tenderly

> Documentation Index
> -------------------
> 
> Fetch the complete documentation index at: [/llms.txt](https://docs.tenderly.co/llms.txt)
> 
> Use this file to discover all available pages before exploring further.

[Skip to main content](https://docs.tenderly.co/developer-explorer/overview#content-area)

Developer Explorer is a suite of Web3 development tools that allow you to inspect and debug transactions coming from any contract or wallet. These tools are available across all the [networks supported on Tenderly](https://docs.tenderly.co/platform/supported-networks)
.

Transaction Listing
-------------------

View all the transactions coming from your contracts and wallets in a unified list.

Inspect Transaction
-------------------

Analyze transaction details, call trace, state changes, events, and more.

Debugger
--------

Identify and fix smart contract issues efficiently with a visual debugging tool.

Gas Profiler
------------

Examine contract gas usage by function and opcode visually with a flame chart.

Simulator UI
------------

Test transaction outcomes by adjusting parameters and simulating results.

Alerts
------

Receive real-time notifications about events on your contracts or wallets.

[​](https://docs.tenderly.co/developer-explorer/overview#getting-started-with-developer-explorer)

Getting started with Developer Explorer
--------------------------------------------------------------------------------------------------------------------------------------------

![Transaction Overview](https://mintcdn.com/tenderly/8ACOAR8iGyQOJzee/images/developer-explorer/overview/transaction-overview.webp?w=2500&fit=max&auto=format&n=8ACOAR8iGyQOJzee&q=85&s=db113c43105d2ee9de157790f7ab4edd) To unlock the power of Developer Explorer, you first need to add a contract or wallet to a Tenderly project. Start with these guides to learn [how to add and manage contracts](https://docs.tenderly.co/developer-explorer/contracts)
 and [how to add and manage wallets](https://docs.tenderly.co/developer-explorer/wallets)
. Tenderly will pull all the transactions from those contracts and wallets and display them on the [Transaction Listing](https://docs.tenderly.co/developer-explorer/transaction-listing)
 page. This gives you an easy overview of the activity and allows you to:

*   [Inspect individual transactions](https://docs.tenderly.co/developer-explorer/inspect-transaction/overview)
    
*   [Debug transaction errors](https://docs.tenderly.co/debugger/overview)
    
*   [Check gas usage](https://docs.tenderly.co/debugger/gas-profiler)
    

Was this page helpful?

YesNo

⌘I

Assistant

Responses are generated using AI and may contain mistakes.

[Contact support](mailto:support@tenderly.co)

---