# Blockscout Transaction Blob Data Fetcher

> Blockscout Transaction Blob Data Fetcher is a paid API for AI agents from api.blockscout.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-10).

Retrieves EIP-4844 blob data associated with a specific transaction on a given blockchain network via Blockscout's multichain explorer

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/transactions/%7Btransaction_hash_param%7D/blobs
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-transaction-blob-data-fetcher-efcfde96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LZB_h-g2D2MAvZ8N0qoww

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 blockscout-transaction-blob-data-fetcher-efcfde96
```

Example prompt: Can you pull up the blob data for transaction 0x3a9f...c4d2 on Ethereum mainnet (chain ID 1) using Blockscout — I need the KZG commitments and proofs attached to it.

## When to prefer this

Use this endpoint when you need to retrieve EIP-4844 blob sidecar data (including KZG proofs and commitments) for a specific transaction on a supported blockchain. Ideal for developers auditing rollup data availability, debugging blob transactions, or verifying proto-danksharding submissions. Prefer this over generic RPC calls when you need structured blob data across multiple chains without managing your own node infrastructure.

## Known failure modes

- Invalid or malformed transaction hash returns an error or empty result
- Chain ID not supported by Blockscout returns 404 or error
- Transaction exists but has no blobs (pre-EIP-4844 or non-blob tx) returns empty items array
- Network timeout if the chain node is slow to respond
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Explore crypto activities with Blockscout's multichain search. Find transactions, addresses, tokens, and dapps across top blockchain networks — your go-to explorer for cross-chain blockchain data

## Output

Returns an array of blob objects associated with the transaction, each containing: blob hash, raw blob data (hex-encoded), KZG proof, and KZG commitment — all fields relevant to EIP-4844 proto-danksharding validation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "chain_id": {
       "type": "string"
      },
      "transaction_hash_param": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "hash": "string",
    "blob_data": "string",
    "kzg_proof": "string",
    "kzg_commitment": "string"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-transaction-blob-data-fetcher-efcfde96/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockscout.com](https://www.zero.xyz/host/api.blockscout.com/llms.txt)