> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> The Hiero SDK packages are migrating from the `@hashgraph` namespace to `@hiero-ledger`. Both currently work; prefer `@hiero-ledger` for new projects and verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# Transactions

> Query transaction history, details, and status on Hedera with the Mirror Node REST API: track payments, token transfers, and smart contract executions.

## Overview

The **Transactions endpoints** in the Hedera Mirror Node REST API allows developers to query **transaction history, details, and status** on the Hedera network. These endpoints is essential for tracking payments, token transfers, smart contract executions, and other network activities.

## Endpoints

The following endpoints are available for the Network activity object:

| **Endpoint**                    | **Description**                                              |
| ------------------------------- | ------------------------------------------------------------ |
| `GET /api/v1/transactions`      | Retrieves a list of transactions on the network.             |
| `GET /api/v1/transactions/{id}` | Fetches details of a specific transaction by transaction ID. |

## Fetching Transactions

The **transaction** object represents the transactions processed on the Hedera network. You can retrieve this to view the transaction metadata information including transaction id, timestamp, transaction fee, transfer list, etc. If a transaction was submitted to multiple nodes, the successful transaction and duplicate transaction(s) will be returned as separate entries in the response with the same transaction ID. Duplicate transactions will still be assessed [network fees](https://www.hedera.com/fees).