# Ethereum Transaction Lookup

> Ethereum Transaction Lookup is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Fetches decoded details of an Ethereum transaction by hash, including sender, receiver, value, gas, block, and function selector

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/eth/tx?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ethereum-transaction-lookup-ad5a68b2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cep-jzVMKES7Q33JQ1Pss

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 ethereum-transaction-lookup-ad5a68b2
```

Example prompt: Look up the Ethereum transaction 0x9531467e03a57bbb5cd080439ac3b10c0cefed147282eb2ff709b02c897afcbf and tell me who sent it, who received it, how much ETH was transferred, and which block it landed in.

## When to prefer this

Choose this endpoint when you need decoded, human-readable details of a specific Ethereum transaction by its hash, including sender, receiver, value, gas, block number, and function selector. Prefer it over raw RPC calls when you want a clean JSON response without setting up a Web3 provider or managing API keys — and payments are only charged on success.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on Ethereum mainnet returns a not-found error
- Network timeout or RPC node unavailability causes a failure (not charged)
- Hash from a different unsupported chain may return no result

## How this service works

Look up an Ethereum transaction by hash: sender, recipient, value in ETH, nonce, gas limit, the 4-byte function selector and its block. Use to see what was sent or whether it exists; for success or failure and fees paid use eth_receipt, for emitted events eth_logs. Input is a 0x-prefixed 64-hex hash; an unknown hash returns 404, uncharged.

## Output

A JSON object containing the transaction hash, from/to addresses, ETH value, gas limit, block number, chain name and chain ID, nonce, the 4-byte function selector (if a contract call), and the number of input bytes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "hash"
 ],
 "properties": {
  "hash": {
   "type": "string",
   "description": "0x-prefixed transaction hash (64 hex characters)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "gas": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "hash": {
   "type": "string"
  },
  "block": {
   "type": "number"
  },
  "chain": {
   "type": "string"
  },
  "nonce": {
   "type": "number"
  },
  "value": {
   "type": "string"
  },
  "chainId": {
   "type": "number"
  },
  "selector": {
   "type": "string"
  },
  "inputBytes": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ethereum-transaction-lookup-ad5a68b2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)