trace
trace_filter
Returns traces matching a filter. Allows searching for specific trace activity across a range of blocks.
Returns traces matching a filter. Allows searching for specific trace activity across a range of blocks.
Parameters
| # | Type | Description |
|---|---|---|
| 1 | object | Filter object specifying the search criteria. |
Filter Object
| Field | Type | Description |
|---|---|---|
fromBlock | string | (required) Start block number as hex string. |
toBlock | string | (required) End block number as hex string. |
fromAddress | array | (optional) Array of sender addresses to filter by. |
toAddress | array | (optional) Array of recipient addresses to filter by. |
after | number | (optional) Offset — skip the first N matching traces. |
count | number | (optional) Maximum number of traces to return. |
Returns
| Type | Description |
|---|---|
array | Array of trace objects matching the filter criteria (same format as trace_block). |
Example
curl -s -X POST https://rpc.pulsechain.box \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "trace_filter",
"params": [{
"fromBlock": "0x100",
"toBlock": "0x200",
"toAddress": ["0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39"],
"count": 10
}],
"id": 1
}'
{
"jsonrpc": "2.0",
"id": 1,
"result": [
{
"action": {
"callType": "call",
"from": "0x...",
"gas": "0x...",
"input": "0x...",
"to": "0x2b591e99afe9f32eaa6214f7b7629768c40eeb39",
"value": "0x..."
},
"blockHash": "0x...",
"blockNumber": 257,
"result": {
"gasUsed": "0x...",
"output": "0x..."
},
"subtraces": 0,
"traceAddress": [],
"transactionHash": "0x...",
"transactionPosition": 0,
"type": "call"
}
]
}
TRY IT
Notes
- Always use
countto limit results. Scanning large block ranges without a limit can time out or return enormous responses. - Use
afterandcountfor pagination through large result sets. - At least one of
fromAddressortoAddressis recommended to narrow results. - Scanning very large block ranges (thousands of blocks) is resource-intensive. Keep ranges small when possible.
- All trace requests are routed to a an archive node with full trace support.