Transaction history by address
Ethereum nodes cannot answer "list transactions for this address". The indexer builds that index for you and keeps it current.
What it does
Index native ETH and ERC-20 transfers into PostgreSQL and serve address transaction history through a read-only PostgREST API. No third-party service, no telemetry, no vendor lock-in.
Ethereum nodes cannot answer "list transactions for this address". The indexer builds that index for you and keeps it current.
What it does
Connects to Geth, Nethermind, Besu, or Erigon over HTTP, WebSocket, or IPC. Any EVM chain with a compatible JSON-RPC endpoint can be indexed.
Architecture
Data lives in a table you own. Query it with SQL, back it up with your existing tooling, or expose it through the bundled read-only REST API.
Database reference
PostgREST serves filtering, ordering, and pagination over the indexed table without writing a line of API code.
API reference
Start from any block height, pick a minimal index set, and optionally store only the addresses you care about.
Address filter
Pull the published container image, run the full Docker Compose stack, or install as a systemd service on bare metal.
Docker image
The indexer is a backend building block for anything that needs Ethereum transaction history by address:
These pages cover the indexer itself: deployment, configuration, database layout, and the REST API contract. Ethereum protocol concepts and execution-client operation stay with the upstream client documentation, and PostgREST query syntax is documented in the PostgREST API reference.
ADAMANT runs this indexer in production for its wallets. That deployment is documented as a real-world integration example on Used by ADAMANT, not as a requirement.