# Base Mainnet Transaction Status Checker

> Base Mainnet Transaction Status Checker is a paid API for AI agents from biosfera.46-62-215-147.sslip.io, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-30).

Looks up the status, block details, gas usage, and total fee (L2 + L1) for a Base mainnet transaction hash

## Facts

- Endpoint: GET https://biosfera.46-62-215-147.sslip.io/o/base-tx?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-mainnet-transaction-status-checker-64b7517c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NLvTRTdObaaNGYFuTjmKS

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 base-mainnet-transaction-status-checker-64b7517c
```

Example prompt: Can you check whether transaction 0x3a1b2c4d5e6f7890abcdef1234567890abcdef1234567890abcdef1234567890ab went through on Base mainnet — did it succeed or revert, and what were the gas fees?

## When to prefer this

Use this endpoint when you specifically need to verify a Base mainnet (chain ID 8453) transaction and require both L2 execution fee and L1 data fee breakdown alongside confirmation count and participant addresses. Prefer this over generic block explorers when operating programmatically in an agent workflow that needs structured JSON output rather than HTML.

## Known failure modes

- Transaction hash not found on Base mainnet — returns does-not-exist status
- Malformed hash (not matching ^0x[0-9a-fA-F]{64}$) results in validation error
- Transaction is still pending — status returned as pending with no block/gas data yet
- Network or RPC unavailability may cause timeout or service error
- Hash from a different chain (e.g. Ethereum mainnet) will return not found

## How this service works

Use when you need to confirm whether a Base mainnet transaction hash succeeded, reverted, is pending or does not exist, with block, confirmations, sender, recipient, gas used and total fee in ETH (L2 plus L1 data fee). Read-only, public blockchain data.

## Output

Returns the transaction status (success, reverted, pending, or not found), the block number it was included in, the number of confirmations, sender and recipient addresses, gas used, and the total fee in ETH broken down into L2 execution fee and L1 data fee.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "pattern": "^0x[0-9a-fA-F]{64}$",
       "description": "transaction hash"
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-mainnet-transaction-status-checker-64b7517c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from biosfera.46-62-215-147.sslip.io](https://www.zero.xyz/host/biosfera.46-62-215-147.sslip.io/llms.txt)