# EVM Block Transaction Count

> EVM Block Transaction Count is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Returns the number of transactions contained in a specified block on a given EVM-compatible chain

## Facts

- Endpoint: POST https://twin.unykorn.org/evm-block-tx-count?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-block-transaction-count-b71eb7fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yIiuvMPpPN91aPFik2XDC

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 evm-block-transaction-count-b71eb7fb -d '<json body>'
```

Example prompt: How many transactions were included in block 21000000 on Ethereum?

## When to prefer this

Choose this endpoint when you need a lightweight, single-number lookup of how many transactions are in a specific EVM block across 10 supported chains (Ethereum, Base, Polygon, Arbitrum, Optimism, BSC, Avalanche, Gnosis, Linea, Scroll). It is more efficient than fetching full block data when only the transaction count is needed. Prefer it for analytics, monitoring, or comparison tasks where you need transaction volume per block without full transaction details.

## Known failure modes

- Invalid block identifier (non-existent or malformed block number/hash) returns an error
- Unsupported chain value outside the allowed enum returns a validation error
- Network or RPC node unavailability for the requested chain may cause a timeout or error
- Payment failure via x402 protocol prevents the call from completing
- Missing required 'chain' or 'block' parameters returns a schema validation error

## How this service works

How many transactions are in a block — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok:true, a type field set to 'evm-block-tx-count', a payment receipt (tx_hash, amount_usd, receipt_id), and a generated_at ISO 8601 timestamp. The transaction count for the specified block on the specified chain is included in the response payload.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "block": {
     "type": "string"
    },
    "chain": {
     "enum": [
      "ethereum",
      "base",
      "polygon",
      "arbitrum",
      "optimism",
      "bsc",
      "avalanche",
      "gnosis",
      "linea",
      "scroll"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "evm-block-tx-count",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.25,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-block-transaction-count-b71eb7fb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)