Check transaction status

post

https://api.mevx.io/swap/api/v1/transaction/status

Check one or more transaction signatures or hashes.

Send hashes and the chain on which they were submitted. Results correspond to the requested entries and use these statuses:

Status	Meaning
`pending`	No final result is available yet
`processed`	Solana processed the transaction
`confirmed`	The chain reports confirmation
`finalized`	Solana reports finalization
`failed`	The chain reports execution failure; inspect `err`

For EVM chains, the current API reports pending, confirmed, or failed. Poll with exponential backoff and choose the confirmation threshold appropriate for your application.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Create a plaintext JSON object containing the chain and transaction identifiers, then encrypt it.

The HTTP body is encrypted text. Before encryption, create this JSON object:

Decrypted JSON field	Required	Description
`chain`	Yes	Chain where the transactions were submitted: `sol`, `eth`, `bsc`, or `base`
`hashes`	Yes	Non-empty array of Solana Base58 signatures or 0x-prefixed EVM transaction hashes

Plaintext example:

{
  "chain": "sol",
  "hashes": ["TRANSACTION_SIGNATURE"]
}

Stringify this object, encrypt it as AES-256-GCM using 12-byte nonce || ciphertext || 16-byte tag, encode it with unpadded Base64URL, and send that string as the text/plain body. The ReadMe Node.js sample performs these steps.

Responses

200Transaction status retrieved successfully

400Bad request - Invalid parameters

401Unauthorized - missing, invalid, or expired API key

429Rate limit exceeded - too many requests

500Internal server error - unexpected system error