Open Parsed Events, choose an active Relay API key, and paste 1–10 confirmed Solana Mainnet transaction signatures. The console sends a request only when you select Parse transactions.
This product requires an active paid plan with a positive DAS/enhanced request limit and an enabled Parsed Events service. The console shows the current availability for your account.
Relay exposes transaction lookup at this route. Address-history lookup, Scan, Query and program discovery are not exposed. These limits describe the Relay API, which supports a smaller interface than the upstream product.
The response is an array with a result for each signature. Check each item’s parserStatus, then read its parsed data or parserError. A successful HTTP response does not mean every transaction decoded successfully.
Decoded content can include instructions, transfers and a summary. Availability depends on the transaction and decoder. Preserve raw integer amounts without rounding them through floating-point arithmetic in your application.
Each forwarded request costs 10 Relay credits, including a request containing multiple signatures. Requests share your plan’s DAS/enhanced request limit with DAS calls. Credits come from the same paid balance used by your other products. Invalid local requests that are not forwarded do not consume these credits.
Open Usage and choose Parsed Events to inspect requests and credits. The request-history method is parsedEvents.transactions. A cancelled browser preview may already have reached the upstream service; check Usage before trying again.