trace_filter

Scans a range of blocks for Parity-style traces matching your filter — addresses and topics — and returns them in one call. It is the range-scan half of the Parity trace trio (with trace_block for whole blocks and trace_transaction for single transactions).

This is the method indexers reach for when receipts are not enough: Safe's Transaction Service, for example, uses trace_filter to find internal transfers while indexing non-L2 Safe deployments. Availability is the most uneven of any method we probe — OP Stack and most zk chains dropped the trace namespace entirely, and some providers gate what remains. Querying old block ranges requires archive access (append &archive=1 on paid plans).

Example request

curl -s https://rpc.swiftnodes.io/rpc/eth?key=YOUR_API_KEY \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"trace_filter","params":[{"fromBlock":"latest","toBlock":"latest"}]}'

Replace YOUR_API_KEY with your SwiftNodes key (free tier available).

Chain support — 32/107 chains

Auto-probed 2026-10-11 through the real customer path (auth, routing, failover). ✓ served · ± served by some upstreams of that chain · ✗ unavailable. Full matrix: method support.