# Saylor Innovations EVM Transaction Details (Arbitrum)

> Saylor Innovations EVM Transaction Details (Arbitrum) is a paid API for AI agents from saylorinnovations.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-03).

Fetches on-chain transaction details for a given transaction hash on the Arbitrum network

## Facts

- Endpoint: GET https://saylorinnovations.com/api/evm/arbitrum/tx/:hash?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/saylor-innovations-evm-transaction-details-arbitrum-dd3bf637
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5od1C1PVxe6ZEbUug-j3I

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 saylor-innovations-evm-transaction-details-arbitrum-dd3bf637
```

Example prompt: Can you look up the on-chain details for Arbitrum transaction hash 0x4e8a3f1c2b... — I need to know the sender, receiver, value, gas used, and whether it confirmed successfully?

## When to prefer this

Choose this endpoint when you need to look up Arbitrum-specific transaction details by hash and want a simple, pay-per-call REST interface without managing your own RPC node or API keys for Alchemy/Infura. It is well-suited for agents performing spot lookups, payment verification, or ledger reconciliation on Arbitrum.

## Known failure modes

- Transaction hash not found — returns 404 or empty result if the hash does not exist on Arbitrum
- Invalid hash format — returns an error if the hash is malformed or not a valid 32-byte hex string
- Network issues — upstream RPC node timeouts may cause delayed or failed responses
- Transaction pending — may not return full details if the transaction is not yet confirmed
- Wrong network — hash exists on a different EVM chain (e.g. Ethereum mainnet) but not Arbitrum

## How this service works

EVM Transaction Details (arbitrum). Arbitrum transaction details: status, from/to, value, block, nonce, gas used, total fee (incl. L1 data fee on OP-stack chains), event count and method selector.

## Output

Returns structured on-chain transaction data for the specified Arbitrum transaction hash, including sender and recipient addresses, ETH value transferred, gas used and gas price, block number, transaction status (success/failure), and timestamp.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/saylor-innovations-evm-transaction-details-arbitrum-dd3bf637/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from saylorinnovations.com](https://www.zero.xyz/host/saylorinnovations.com/llms.txt)