# Blockchain Transaction Status Lookup

> Blockchain Transaction Status Lookup is a paid API for AI agents from x402-stock-indicators.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Looks up the on-chain status of a transaction by hash, returning whether it succeeded, failed, or is unrecognized on the specified chain.

## Facts

- Endpoint: GET https://x402-stock-indicators.vercel.app/transaction-status/%7Btx_hash%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchain-transaction-status-lookup-8dbee271
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_stUIr2omWSunWYzHdbSl3

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 blockchain-transaction-status-lookup-8dbee271
```

Example prompt: Can you check whether this Ethereum transaction went through — the hash is 0x4dfa7b1be6578326be24ad2d330e7baf23230e18c2d2c67d8f41798e0e764b0b?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a specific on-chain transaction succeeded or failed, particularly for Ethereum mainnet. Ideal for agents that need to confirm payment receipts, debug contract reverts, or validate that a submitted transaction was mined successfully without requiring an API key or subscription.

## Known failure modes

- Transaction hash not found on Etherscan returns succeeded: null with a note about unrecognized hashes
- Pre-Byzantium transactions (before block 4,370,000) return succeeded: null because the receipt status field did not exist
- Invalid or malformed tx_hash may return an error or null result
- Payment failure via x402 protocol if USDC balance is insufficient

## How this service works

Pay-per-call stock, macro, on-chain, and crypto data over the x402 protocol. USDC on Base or Solana, no API keys, no subscriptions.

## Output

Returns a JSON object with the chain identifier, the transaction hash, a boolean indicating whether the transaction succeeded (null for pre-Byzantium or unrecognized hashes), an error_description if applicable, and whether the failure was a contract-level error (revert).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "succeeded is null for pre-Byzantium transactions (before block 4,370,000) or a tx hash Etherscan doesn't recognize -- the receipt status field didn't exist yet.",
  "chain": "eth",
  "tx_hash": "0x4dfa7b1be6578326be24ad2d330e7baf23230e18c2d2c67d8f41798e0e764b0b",
  "succeeded": true,
  "error_description": null,
  "is_contract_error": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchain-transaction-status-lookup-8dbee271/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-stock-indicators.vercel.app](https://www.zero.xyz/host/x402-stock-indicators.vercel.app/llms.txt)