Ask for one address and get its identities, balances and merged activity in one response, so you stop joining the chain side and the LayerX side by hand. Ask for one transaction and get the settlement rung it reached. Four paxeer-x routes serve capabilities, anchors and receipts. Bring the stack up locally from one Docker Compose file: Postgres, backend, frontend and both Rust services, built from the repository. lx_receipts stays empty, since the kernel history ingester is not written.

What it does

The Paxeer X Network explorer is a fork of Blockscout: backend v10.2.6, frontend v2.7.2, and two vendored Rust services from blockscout-rs (smart contract verifier and signature provider). On top of that it adds five read endpoints for Paxeer X data, five lx_* database tables filled from kernel precompile logs, and a paxeer_x JSON-RPC variant that records where the node's answers diverge from Ethereum's. A single Docker Compose file builds and runs the whole stack from the sources in the repository: Postgres, backend, frontend and both Rust services.

Key capabilities

• GET /api/v2/addresses/:hash/unified returns one account's identities, balances and merged activity.
• GET /api/v2/transactions/:hash/status returns the settlement rung a transaction has reached.
• GET /api/v2/paxeer-x/capabilities, /anchors, /receipts and /receipts/:id serve LayerX data.
• Five lx_* tables carry account bindings, custody events, anchors, receipts and market events.
• The paxeer_x JSON-RPC variant documents and handles four node-specific divergences.
• One compose file builds Postgres, backend, frontend and both Rust services locally.

Differentiators

The unified account endpoint returns identities, one asset list where each asset carries a single total beside its chain, custody and kernel parts, and one activity feed merging chain transactions and token transfers with LayerX kernel events. The paxeer_x variant is the one place that states each divergence of the node's RPC and the handling it requires.

Outcomes

• Get one account's identities, balances and merged activity in one response
• Check a transaction's settlement rung with a single request
• Run the full explorer stack locally from one Docker Compose file

Technical notes

• Backend needs Elixir 1.19.4-otp-27, Erlang 27.3.4.6 and PostgreSQL 16; it serves port 4000 and the frontend serves port 3000. Set ETHEREUM_JSONRPC_VARIANT=paxeer_x, CHAIN_ID, DATABASE_URL and a SECRET_KEY_BASE of at least 64 bytes. The frontend needs Node.js 22 or newer.
• The local compose file takes RPC_HTTP_URL, RPC_WS_URL, CHAIN_ID and SECRET_KEY_BASE from the shell with no default; an empty CHAIN_ID or SECRET_KEY_BASE stops the container rather than starting it with a stand-in. RPC defaults point at host.docker.internal:8545. Ports 7432, 4000 and 3000 are published to the host, and every service has a health check.
• The three frontend pages (/paxeer-x/receipts, /paxeer-x/anchors and /paxeer-x/account/:hash) are behind NEXT_PUBLIC_PAXEER_X_ENABLED, which defaults to false.
• Hosted deployment is defined for Railway only: four services in one project, with the backend health check allowed 600 seconds so a fresh database can run every migration first. There is no Kubernetes or Terraform configuration under explorer/.
• The LayerX precompiles are not on the chain that is live now, so /capabilities probes the node every 30 seconds and reports a surface as false until eth_getCode answers with code. lx_receipts is never filled by the indexer: a kernel receipt is not an EVM event, and the kernel history ingester that would fill the table is not written.
• Range partitioning of logs and token_transfers is not delivered; the database notes record it as blocked on the tables' primary keys, a nullable partition key and the absence of a job that creates partitions.
• DATABASE_READ_ONLY_API_URL routes API reads to a read-only replica, falling back to the primary when replay lag exceeds REPLICA_MAX_LAG (five minutes by default).
• Licensing: everything under explorer/ is GPL-3.0 except the vendored Rust services, which stay MIT. Neither tree is linked into the Apache-2.0 crates and Go packages in the rest of the repository.

RPC_HTTP_URL=http://127.0.0.1:8545/ RPC_WS_URL=ws://127.0.0.1:8546/ \
CHAIN_ID=125 SECRET_KEY_BASE="$(openssl rand -base64 48)" \
  docker compose -f explorer/deploy/docker-compose.local.yml up --build

curl http://localhost:4000/api/v2/paxeer-x/capabilities
curl http://localhost:4000/api/v2/paxeer-x/anchors
curl http://localhost:4000/api/v2/addresses/0xYourAddress/unified
curl http://localhost:4000/api/v2/transactions/0xYourTxHash/status

More in Developers