> For the complete documentation index, see [llms.txt](https://docs.phron.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phron.ai/developers/build-with-phronai/smart-contracts-development/solidity-contracts/phron-toolkit/json-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 for deeper insight into transaction processing. Some of these non-standard RPC methods are supported as part of Phron's goal of providing a seamless Ethereum experience for developers. Supporting these RPC methods is an essential milestone because many projects like [The Graph](https://thegraph.com/) rely on them to index blockchain data.

This guide will cover the supported RPC methods available on Phron and how to invoke them using curl commands against a tracing node with the debug, txpool, and tracing flags enabled. You can access a tracing node in one of two ways: through a supported tracing RPC provider or by spinning up a tracing node of your own.

To view a list of tracing RPC providers, please check out 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://docs.phron.ai/developers/build-with-phronai/smart-contracts-development/solidity-contracts/phron-toolkit/json-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.