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

# getTransactions | TON v2

> The getTransactions method retrieves the transaction history for a specific address on the TON blockchain. Chainstack TON v2 reference.

The `getTransactions` method retrieves the transaction history for a specific address on the TON blockchain. This method allows you to fetch a list of transactions associated with an address, with options to limit the number of results and specify the starting point of the search.

<Note>
  **TON billing: this method is always archive (2 RUs)**

  Account transaction history can reach arbitrarily far back, so this method is always billed as archive. See [Request units — TON method scope](/docs/request-units#ton-method-scope).
</Note>

## JSON-RPC example

```shell Shell theme={"system"}
curl -X POST \
  'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2/jsonRPC' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getTransactions",
    "params": {
      "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2",
      "limit": 10,
      "to_lt": 0,
      "archival": false
    }
  }'
```

## Parameters

* `address` (string, required) — The address for which to retrieve transactions. Example: `EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2`.
* `limit` (integer, optional) — The maximum number of transactions to return. Default: 10.
* `to_lt` (integer, optional) — The logical time to start the search from (0 means from the latest). Default: 0.
* `archival` (boolean, optional) — Whether to use an archival node for the query. Default: false.

## Response

An array of transaction objects, each containing:

* `transaction_id` (object) — The unique identifier of the transaction, containing:
  * `lt` (string) — The logical time of the transaction.
  * `hash` (string) — The hash of the transaction.
* `utime` (integer) — Unix timestamp of the transaction.
* `fee` (string) — The fee for the transaction in nanotons.
* `storage_fee` (string) — The storage fee for the transaction in nanotons.
* `other_fee` (string) — Other fees for the transaction in nanotons.
* `transaction_type` (string) — The type of the transaction.
* `compute` (object) — Computation details of the transaction.
* `action` (object) — Action details of the transaction.
* `in_msg` (object) — Details of the incoming message.
* `out_msgs` (array) — Details of the outgoing messages.

## Use case

A possible use case for the `getTransactions` method in TON is for blockchain explorers or wallet applications that need to display transaction history for a specific address. This method can be used to show recent transactions, calculate total incoming/outgoing amounts, or analyze transaction patterns for a given address.


## OpenAPI

````yaml openapi/ton_node_api/v2/getTransactions.json GET /getTransactions
openapi: 3.0.0
info:
  title: getTransactions example
  version: 1.0.0
  description: >-
    This is an API example for getTransactions, a method to retrieve transaction
    history for a specific address on the TON blockchain.
servers:
  - url: >-
      https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v2
security: []
paths:
  /getTransactions:
    get:
      tags:
        - TON Operations
      summary: getTransactions
      operationId: getTransactions
      parameters:
        - name: address
          in: query
          required: true
          description: The address to get transactions for
          schema:
            type: string
            default: EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2
          example: EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2
        - name: limit
          in: query
          required: false
          description: The maximum number of transactions to return
          schema:
            type: integer
            default: 10
          example: 10
        - name: to_lt
          in: query
          required: false
          description: The logical time to start the search from (0 means from the latest)
          schema:
            type: integer
            default: 0
          example: 0
        - name: archival
          in: query
          required: false
          description: Whether to use archival node for the query
          schema:
            type: boolean
            default: false
          example: false
      responses:
        '200':
          description: Transaction history for the specified address
          content:
            application/json:
              schema:
                type: array
                items:
                  type: object
                  properties:
                    transaction_id:
                      type: object
                      properties:
                        lt:
                          type: string
                          description: The logical time of the transaction
                        hash:
                          type: string
                          description: The hash of the transaction
                    utime:
                      type: integer
                      description: Unix timestamp of the transaction
                    fee:
                      type: string
                      description: The fee for the transaction in nanotons
                    storage_fee:
                      type: string
                      description: The storage fee for the transaction in nanotons
                    other_fee:
                      type: string
                      description: Other fees for the transaction in nanotons
                    transaction_type:
                      type: string
                      description: The type of the transaction
                    compute:
                      type: object
                      description: Computation details of the transaction
                    action:
                      type: object
                      description: Action details of the transaction
                    in_msg:
                      type: object
                      description: Details of the incoming message
                    out_msgs:
                      type: array
                      description: Details of the outgoing messages

````