> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/solana/fast-landing/transaction-errors.md).

# Transaction error details

## API Info

* **Method:** GET
* **URL:** `/api/v1/tx/error-details/{tx_hash}`
* **BaseURL:** `https://node1.me`
* **Authorization:** NO

## Request Example

★ tx\_hash placeholder for query transaction signature

```bash
curl https://node1.me/api/v1/tx/error-details/{tx_hash}
```

## Parameter Description

| Parameter | Type   | Required | Description                                                                                                        |
| --------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------ |
| tx\_hash  | string | ✅        | Transaction Signature (base58). Can be obtained from the transaction submission response or on the Solana browser. |

To troubleshoot multiple transactions, you can use for tx in ...; do curl ...; done in shell and appropriately control the frequency with sleep.

## Response Example

// Transaction details found

```json
{
  "success": true,
  "code": 200,
  "message": [
    "Transaction failed: Transaction is not recent"
  ]
}
```

// Transaction not found

```json
{
  "success": false,
  "code": 500,
  "message": "Transaction not found"
}
```

## Response Fields

* No authentication required, suitable for quick troubleshooting, but still control the query frequency to avoid triggering rate limiting.
* The message field is consistent with Solana RPC errors. Referencing the Error Code will help you diagnose issues more efficiently.
* If Transaction not found is returned, it is typically due to an incorrect signature or the transaction not yet being archived. Please try again later.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://node1.gitbook.io/node1-docs/solana/fast-landing/transaction-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.