# OneSource Ethereum Transaction Lookup by Hash

> OneSource Ethereum Transaction Lookup by Hash is a paid API for AI agents from skills.onesource.io, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-15).

Fetches full Ethereum transaction details (from, to, value, calldata, block) for a given transaction hash using eth_getTransactionByHash

## Facts

- Endpoint: GET https://skills.onesource.io/api/chain/tx/:hash
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/skills-onesource-io-52887840
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VS9h1mb1yBFpJMPOiZz-6

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 skills-onesource-io-52887840
```

Example prompt: Can you pull the full details for Ethereum transaction 0x4e3a3754410177e6937ef1f84bba68ea139e8d1b79cf9428e46fe41aa2e3e83f — I want to see the sender, receiver, value, calldata, and which block it landed in?

## When to prefer this

Use this endpoint when you need raw, full transaction details (from, to, value, input/calldata, block) for a known tx hash on Ethereum or supported EVM networks (sepolia, Base, Avalanche, MegaETH). Prefer this over a receipt endpoint when you need input data or pre-execution fields rather than post-execution logs and status.

## Known failure modes

- Transaction hash not found on the specified network — returns null or 404
- Invalid hash format (not 0x-prefixed 64-char hex) — returns validation error
- Network not supported or unavailable — returns error
- Transaction exists on a different network than specified — returns null
- RPC node timeout or rate limit — returns 5xx error

## How this service works

Full Ethereum transaction details by hash via eth_getTransactionByHash - from, to, value, calldata, block

## Output

Returns a JSON object with the full transaction details including from address, to address, ETH value transferred, calldata/input data, gas fields, nonce, block number, and transaction index — as returned by eth_getTransactionByHash on the specified EVM network.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/skills-onesource-io-52887840/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from skills.onesource.io](https://www.zero.xyz/host/skills.onesource.io/llms.txt)