> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/12-11-2026-transaction-lookup-native-hash-formats.md).

# 12-11-2026: Transaction Lookup Accepts Each Chain's Native Hash Format

`POST /api/v1/transaction-with-token-transfer-lookup` accepted only a `0x`-prefixed, 64-character hex hash on every chain. Tron and Bitcoin hashes have no `0x` prefix, and adding one to pass validation made the request fail with a `500`. Sui and NEAR hashes are base58, so they could not be looked up at all.

**`transaction_hash` now takes the hash in the form each chain uses:**

| Chain                          | Accepted `transaction_hash`             |
| ------------------------------ | --------------------------------------- |
| EVM chains and `all`           | `0x` + 64 hex characters (unchanged)    |
| `tron`, `bitcoin`, `injective` | 64 hex characters, with or without `0x` |
| `starknet`                     | `0x` + up to 64 hex characters          |
| `sui`, `near`                  | Base58 transaction digest               |

Hex hashes are case-insensitive. A hash in the wrong format for the chain returns a `422` validation error that names the expected format, instead of a `500`. `block_timestamp` stays required for non-EVM chains; a base58 hash sent without it returns a `422`. On Injective, a hash sent without `0x` is treated as a native (non-EVM) transaction and also needs `block_timestamp`, or the request returns a `422`. A `0x` hash there is treated as an EVM transaction, and `block_timestamp` stays optional.

**NEAR no longer accepts a `0x` hex hash.** Send the base58 hash with `block_timestamp`. A `0x` hash never matched a NEAR transaction, so no request that returned data before is affected.

Example, a Tron transaction:

```bash
curl -X POST "https://api.nansen.ai/api/v1/transaction-with-token-transfer-lookup" \
  -H "Content-Type: application/json" \
  -H "apikey: YOUR_API_KEY" \
  -d '{"chain": "tron", "transaction_hash": "8034aaf8c3e0db8095af6f6520469347ee94f8753055e954c0d65b52923c92a5", "block_timestamp": "2026-11-10 00:43:45"}'
```

Tron, Injective and NEAR lookups now return the transaction. Bitcoin lookups no longer fail but return no transaction yet, and Sui and Starknet lookups still return an error. We will announce when those chains return data.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/12-11-2026-transaction-lookup-native-hash-formats.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
