Back to Browse
Blockchain.info Solana Block Transactions API
x402
Blockchain.info Solana Block Transactions API is a paid API for AI agents from api.blockchain.info, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).
Retrieves a paginated list of transactions within a specific Solana block, sortable by index or fee
Price / call$0.003
Success—
StatusUnknown
How this service works
Paid AI-agent access to Blockchain.com Explorer API
Output
Returns a paginated list of transactions for the specified Solana block, including transaction identifiers, fees, and block position indices. Results respect the requested sort field (index or fees), order (asc/desc), limit (up to 50), and offset. An offset beyond the total transaction count returns an empty page rather than an error.
Example use cases
Analyze high-fee transactions in a block
“Show me the top 10 transactions by fee in Solana block 290000000 — I want to see which transactions paid the most.”
Paginate through all block transactions
“I need to page through all transactions in Solana block 295000000 in order — give me 50 at a time starting from the beginning, sorted by block position index.”
Audit a specific Solana block
“Fetch the transactions in SOL block 301234567 so I can audit everything that happened in that block — show up to 25 transactions sorted ascending by index.”
Technical details
Endpoint
POSThttps://api.blockchain.info/explorer-gateway-kt/x402/sol/block/transactions?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need structured, paginated access to all transactions within a specific Solana block from the Blockchain.com Explorer, especially when you want to sort by fee or block position index. Prefer this over generic RPC calls when you need clean pagination semantics (no duplicate or skipped transactions) and a predictable JSON response. Best suited for block-level analysis, auditing, or fee research on Solana.
Side effects
- Invalid blockId returns a 404 or empty result
- sort=value is not supported on SOL and returns 400
- limit above 50 is rejected as out of range
- Missing or invalid network parameter may cause a 400 error
- Payment failure or insufficient USDC balance blocks the request via x402
- Very large offsets beyond total transaction count return empty pages silently
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| sort | string | `index` orders by position in the block, `fees` by `fee`. Ties always fall back to block position, so paging can neither duplicate nor skip a transaction. `sort=value` is not supported on SOL and returns 400. |
| limit | integer | Page size (capped at 50) |
| order | string | |
| offset | integer | Offset into the sorted transaction list. An offset beyond `total` returns an empty page, not an error. |
| blockId | integer | |
| network | string |
Output
Schema · Response
{
"type": "json",
"format": "application/json"
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"