> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/developer-docs/rpc/reference/debug_tracetransaction.md).

# debug\_traceTransaction

## Summary

Replays a transaction in its original block context and returns an execution trace. The public MegaETH endpoint supports this standard debug method.

## Parameters

| Position | Name              | Type             | Required                  | Description                                                                   |
| -------- | ----------------- | ---------------- | ------------------------- | ----------------------------------------------------------------------------- |
| `0`      | `transactionHash` | `DATA`, 32 bytes | Yes                       | Hash of a mined transaction.                                                  |
| `1`      | `traceConfig`     | object           | Yes on the public gateway | Tracer selection and tracer-specific options. Use `{}` for the opcode tracer. |

## Result

The result shape depends on the tracer. With no named tracer, the result contains opcode-level `structLogs`; with `callTracer`, it is a nested call frame.

## Comparison with Ethereum Standard JSON-RPC

### Ethereum Standard

The method reconstructs the transaction's pre-execution state, replays the transaction, and returns the selected trace format.

### MegaETH Node Behavior

MegaETH provides geth-compatible opcode and named tracers. Tracing a system transaction may expose MegaETH system-contract calls.

### MegaETH Public Gateway

The public gateway streams this method's response and requires both positional parameters.

## Errors

The `| Scope |` column distinguishes method failures from gateway policy errors.

| Code     | Scope            | Message           | When it happens                                                                         |
| -------- | ---------------- | ----------------- | --------------------------------------------------------------------------------------- |
| `-32602` | Method           | Invalid params    | The hash or trace configuration is missing or malformed.                                |
| `-32000` | Method           | Server error      | The transaction or required history is unavailable, a timeout occurs, or tracing fails. |
| `-32099` | Transport/policy | Payload too large | The request exceeds the public endpoint body limit.                                     |

## Examples

Endpoint: `https://mainnet.megaeth.com/rpc`

Capture date: July 24, 2026

Outcome: success

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "debug_traceTransaction",
  "params": [
    "0xecc262f36652019b75f4cb7315ff19f430fc92efd5a8048948400407d55fd904",
    { "tracer": "callTracer" }
  ]
}
```

The nested call frame is abbreviated below.

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "from": "0xdeaddeaddeaddeaddeaddeaddeaddeaddead0001",
    "to": "0x4200000000000000000000000000000000000015",
    "gas": "0x5f5e100",
    "gasUsed": "0xb9d56c",
    "type": "CALL"
  }
}
```

## Sources

* Spec: [Ethereum Execution APIs, `src/debug/trace.yaml`](https://github.com/ethereum/execution-apis/blob/50d1e5e0b6f5a5046e45421e5c84497ab6e55e6c/src/debug/trace.yaml)
* Probe: MegaETH Mainnet public endpoint, July 24, 2026


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.megaeth.com/developer-docs/rpc/reference/debug_tracetransaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.