# Solana Transaction Explainer

> Solana Transaction Explainer is a paid API for AI agents from solana-pulse-gateway-1021990235790.us-central1.run.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-13).

Reads a confirmed Solana transaction and returns its status, fee, all SOL and token balance changes by wallet, programs invoked, and a decoded failure reason if it failed.

## Facts

- Endpoint: POST https://solana-pulse-gateway-1021990235790.us-central1.run.app/api/tools/explain_transaction?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/solana-transaction-explainer-21b6d406
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C7WlVztTxiWvOQ_5qc7e-

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 solana-transaction-explainer-21b6d406 -d '<json body>'
```

Example prompt: My Solana transaction 5KtP...XQz failed — can you explain what actually happened, which program caused the failure, and what changed across all the wallets involved?

## When to prefer this

Use this endpoint after a Solana transaction has landed or failed, when you need a structured, human-readable breakdown of what actually happened rather than parsing raw logs. It is the right choice when you need to surface failure reasons, identify the specific failing program, or audit all balance changes across wallets without manually decoding instruction data.

## Known failure modes

- Transaction signature not yet confirmed — returns error if transaction is still pending or not found on-chain
- Invalid or malformed transaction signature — returns a parsing or lookup error
- Network timeout reaching Solana RPC — may return a connectivity error
- Transaction too old and pruned from history — may return not found

## How this service works

Use after a transaction lands (or fails) to report what actually happened, instead of guessing from logs. For failures it names the failing program and the fix. Reads a confirmed transaction and returns status, fee, every SOL and token balance change by wallet, the programs used, and a decoded failure reason.

## Output

Returns the transaction status (success/failure), fee paid in lamports, a per-wallet breakdown of every SOL and SPL token balance change, the list of programs invoked, and for failed transactions a human-readable decoded failure reason naming the specific program that failed and the recommended fix.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/solana-transaction-explainer-21b6d406/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from solana-pulse-gateway-1021990235790.us-central1.run.app](https://www.zero.xyz/host/solana-pulse-gateway-1021990235790.us-central1.run.app/llms.txt)