# Explorer Gateway API – Ethereum Block Lookup

> Explorer Gateway API – Ethereum Block Lookup is a paid API for AI agents from api.blockchain.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-01).

Retrieves details for a specific Ethereum block by block hash or block number via blockchain.com's explorer gateway

## Facts

- Endpoint: POST https://api.blockchain.com/explorer-gateway-kt/x402/eth/block?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/explorer-gateway-api-ethereum-block-lookup-97262509
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1QAPMPJt1tKQ79EcxVcUq

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability explorer-gateway-api-ethereum-block-lookup-97262509 -d '<json body>'
```

Example prompt: Can you pull up the details for Ethereum block number 0 — the genesis block — from blockchain.com's explorer gateway on the ETH network?

## When to prefer this

Choose this endpoint when you need to look up a single Ethereum block by its exact hash or block number and want data from a reputable, blockchain.com-hosted explorer gateway. It is ideal for agents that need block-level metadata (miner, gas, timestamp, transactions) on Ethereum mainnet. Prefer it over raw RPC calls when you want a REST/JSON interface without managing your own Ethereum node or API key — and are comfortable with a per-call micropayment via x402.

## Known failure modes

- Neither hash nor blockId provided — request rejected with validation error
- Block not found for given hash or block number — 404 or empty response
- Invalid hash format (not a valid hex string) — 400 bad request
- Block number out of range or negative — validation error
- Network field missing or set to unsupported chain — error response
- Payment not included or insufficient — 402 Payment Required
- Rate limiting or upstream node unavailability — 503 or timeout

## How this service works

Blockchain explorer gateway — Solana, Bitcoin, Bitcoin Cash, Ethereum

## Output

Returns a JSON object containing detailed Ethereum block data, likely including the block hash, block number, timestamp, miner/validator address, gas limit, gas used, transaction count and/or transaction hashes, block reward, parent hash, and other standard Ethereum block header fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "example": "0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3",
   "nullable": true,
   "description": "Block hash; provide this or blockId"
  },
  "blockId": {
   "type": "integer",
   "format": "int64",
   "minimum": 0,
   "nullable": true,
   "description": "Block number (non-negative); provide this or hash"
  },
  "network": {
   "type": "string",
   "example": "ETH"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "format": "application/json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/explorer-gateway-api-ethereum-block-lookup-97262509/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchain.com](https://www.zero.xyz/host/api.blockchain.com/llms.txt)