Skip to main content

Explorer and Indexer REST API

The OXN block explorer at explorer.bout.network is backed by a REST API. This API is what powers the explorer UI, and is also useful directly for indexers, analytics dashboards, and monitoring services.

Base URL​

The API is served at:

https://explorer.bout.network/v1/

All endpoints return JSON.

Common query patterns​

Endpoint paths and specific field names may evolve. Below are typical endpoint shapes; consult the live API for exact schemas.

Blocks​

curl https://explorer.bout.network/v1/blocks?limit=10
curl https://explorer.bout.network/v1/blocks/12345

Returns block metadata: height, hash, timestamp, transaction count, gas used.

Transactions​

curl https://explorer.bout.network/v1/transactions?limit=25
curl https://explorer.bout.network/v1/transactions/0x{tx_hash}

Transaction fields include from, to, value, gas, status. For encrypted transactions, the data field is present but opaque (CBOR envelope bytes).

Accounts​

curl https://explorer.bout.network/v1/accounts/0x{address}

Returns balance, transaction count, and (if a contract) creation transaction.

Events / Allowances​

Domain-specific tables — the exact endpoints depend on what the indexer chose to expose. Standard tables include event logs (encrypted for encrypted transactions) and ERC-20 allowances.

Pagination​

Endpoints returning lists support pagination:

?limit=25&offset=0

or cursor-based:

?limit=25&after=<cursor>

Follow the Link header or next_cursor field in the response for continuation.

Query filtering​

Common filters:

  • ?address=0x... — restrict to a specific account or contract
  • ?from_height=X&to_height=Y — restrict to a block range
  • ?status=success|failed — restrict by transaction status

What the API sees​

The explorer indexer sees the same public chain data that any observer sees:

  • Block and transaction metadata: fully visible.
  • Encrypted calldata: opaque bytes.
  • Encrypted event topics/data: opaque bytes.
  • Contract addresses and bytecode: fully visible.

The indexer cannot decrypt confidential contract state or event contents. It is a public read-side, exactly as you'd expect.

Rate limits​

The REST API applies its own rate limits, similar in shape to the JSON-RPC rate limits — per-IP quotas, 429 Too Many Requests responses. See Rate Limits.

Running your own indexer​

If you need custom indexing (specific events, computed views, cross-referenced data), running your own indexer against the OXN RPC is straightforward. Standard EVM indexers (Ponder, Envio, SubQuery patterns) work as long as they can accept encrypted calldata as opaque bytes.

Next steps​