Skip to content

Transaction was not found (transaction_not_found) ​

HTTP 404Orion /v3 ProblemCode: transaction_not_found
Type URI: https://orion.stellarchain.io/problems/transaction_not_found

No transaction with the given 64-character hex hash exists in ledger history.

How to Resolve transaction_not_found

  1. Inspect the status (404), code (transaction_not_found), and detail fields in the JSON response.
  2. For 400 validation errors (invalid_*), verify query parameters against the Endpoints Reference or Statistics Catalog (GET /v3/statistics).
  3. For 404 errors (*_not_found), confirm the resource exists on Stellar Pubnet.
  4. For 409, 429, 503, or 504 transient states, retry with exponential backoff.

Example Response & Client Handling ​

json
{
  "type": "https://orion.stellarchain.io/problems/transaction_not_found",
  "title": "Transaction was not found",
  "status": 404,
  "detail": "Transaction was not found",
  "code": "transaction_not_found"
}
typescript
const res = await fetch('https://pubnet.stellarchain.io/v3/statistics');
if (!res.ok) {
  const problem = await res.json();
  if (problem.code === 'transaction_not_found') {
    console.error('Orion /v3 Problem [transaction_not_found]:', problem.detail);
  }
}
bash
curl -i -s "https://pubnet.stellarchain.io/v3/statistics" \
  -H "Accept: application/json"

← Back to All 53 Orion /v3 Problem Codes

Open-Source Stellar Horizon & Orion Documentation under MIT License.