> For the complete documentation index, see [llms.txt](https://dev.phron.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.phron.ai/build-with-phronai/sdks-and-tools/ethereum/rpc-apis/non-standard-ethereum-tracing.md).

# Non-standard Ethereum: Tracing

## Debug API & Trace Module <a href="#debug-api-trace-module" id="debug-api-trace-module"></a>

### Introduction <a href="#introduction" id="introduction"></a>

**Geth's** [**`debug`**](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-debug) **and** [**`txpool`**](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-txpool) **APIs** and **OpenEthereum's** [**`trace`**](https://openethereum.github.io/JSONRPC-trace-module) **module** provide non-standard RPC methods that offer deeper insights into transaction processing. Phron supports several of these non-standard RPC methods to ensure a seamless Ethereum-like experience for developers. This support is crucial as many blockchain projects, such as [**The Graph**](https://thegraph.com/), depend on these methods to efficiently index blockchain data.

This guide details the non-standard RPC methods available on Phron, along with instructions on how to invoke them using `curl` commands against a tracing node. To use these RPC methods, ensure that your node is running with the `debug`, `txpool`, and `tracing` flags enabled.

You can access a tracing node in one of two ways:

1. Through a supported tracing RPC provider.
2. By setting up your own tracing node.

For a list of available tracing RPC providers, refer to the **Network Endpoints** page.


---

# 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://dev.phron.ai/build-with-phronai/sdks-and-tools/ethereum/rpc-apis/non-standard-ethereum-tracing.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.