> For the complete documentation index, see [llms.txt](https://docs.shadeprotocol.io/shade-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadeprotocol.io/shade-protocol/get-started/step-5-use-our-features/history-feature/what-is-a-transaction-hash.md).

# What is a transaction hash

#### <mark style="color:purple;">**Transaction hash**</mark>

A transaction hash is a unique identifier that represents a particular transaction on the blockchain. It is a cryptographic hash function applied to the transaction data, which includes details such as the sender's and receiver's addresses, the amount being transferred, and any additional data or metadata.

*Note: Transaction Hash may be shortened to Tx Hash.*&#x20;

#### <mark style="color:purple;">**The primary purposes of a transaction hash**</mark>

1. **Identification:** Each transaction on the blockchain has a unique hash that distinguishes it from all other transactions. This hash serves as an identifier for the transaction.
2. **Verification:** The transaction hash is used to verify the integrity of the transaction data. If any part of the transaction data is modified, even a single bit, the resulting hash will be completely different. This property makes it possible to detect any tampering or corruption of the transaction data.
3. **Indexing and lookup:** Blockchain explorers and wallets use transaction hashes as a way to lookup and reference specific transactions. Users can search for a particular transaction hash to view its details, such as the sender, receiver, amount, and status (confirmed or unconfirmed).<br>

When a new transaction is broadcasted to the blockchain network, its hash is calculated, and the transaction is then included in a block by miners or validators. Once the block is confirmed and added to the blockchain, the transaction hash becomes a permanent record, and the transaction is considered complete and irreversible.

Transaction hashes are an essential component of blockchain technology, providing a secure and tamper-evident way to identify and verify transactions, and enabling transparency and auditability within the cryptocurrency ecosystem.

***

*Information provided in this post is for general informational purposes only and does not constitute formal investment advice. Please read the full disclaimer at* [*shadeprotocol.io/disclaimer*](https://shadeprotocol.io/disclaimer) *before relying on any information herein.*


---

# 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://docs.shadeprotocol.io/shade-protocol/get-started/step-5-use-our-features/history-feature/what-is-a-transaction-hash.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.