Quickstart
Pinax RPC endpoints are standard JSON-RPC 2.0 over HTTPS. Pick a network, embed your API key in the URL path, and POST a JSON-RPC body. Browse the full method catalog below or hit Try it on any method to send a live request.
No API key on this team yet — sample shows YOUR_API_KEY placeholder.
cURL
1curl 'https://eth.rpc.service.pinax.network/v1/YOUR_API_KEY/' \2 -H 'Content-Type: application/json' \3 -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
Supported networks (32)
debug
debug_traceTransaction
KEY REQUIREDTrace transaction execution
Replays a transaction and returns opcode-level execution details, call frames, or another tracer-specific result. Available only on RPC endpoints with Reth archive node support.POST
https://eth.rpc.service.pinax.network/v1/<API_KEY>/
Available only on RPC endpoints with Reth archive node support.
Required parameters
| Name | Type | Description |
|---|---|---|
txHashrequired | hash | 32-byte transaction hash to replay. e.g. 0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b |
Optional parameters
| Name | Type | Description |
|---|---|---|
tracerConfig | json | Optional tracer configuration, such as <code>{"tracer":"callTracer"}</code> or timeout settings. e.g. {"tracer":"callTracer","timeout":"30s"} |
Request body
{
"jsonrpc": "2.0",
"id": 1,
"method": "debug_traceTransaction",
"params": [
"0x88df016429689c079f3b2f6ad39fa052532c56795b733da78a91ebe6a713944b",
"{\"tracer\":\"callTracer\",\"timeout\":\"30s\"}"
]
}Response
200 OKTrace result object. Shape depends on the selected tracer.
{ "jsonrpc": "2.0", "id": 1, "result": { "type": "CALL", "from": "0xd8da6bf26964af9d7eed9e03e53415d37aa96045", "to": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48", "gas": "0x5208", "gasUsed": "0x5208", "input": "0xa9059cbb...", "output": "0x" } }