> ## Documentation Index
> Fetch the complete documentation index at: https://chainstack-docs-polygon-erigon-trace-deprecation.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# transactionsByMasterchainBlock | TON v3

> The transactionsByMasterchainBlock endpoint retrieves a list of transactions for a specific masterchain block in the TON blockchain.

The `transactionsByMasterchainBlock` endpoint retrieves a list of transactions for a specific masterchain block in the TON blockchain. This endpoint allows you to fetch transactions associated with a particular block and provides options for pagination and sorting.

<Note>
  **TON billing: full or archive by block age**

  This method is billed as archive (2 RUs) when the requested block is 128 or more seqno behind the tip, and full (1 RU) otherwise. See [Request units — TON method scope](/docs/request-units#ton-method-scope).
</Note>

## Parameters

* `seqno` (integer, required) — The sequence number of the masterchain block. Example: `40467413`.
* `limit` (integer, optional) — The maximum number of transactions to return. Default: `128`.
* `offset` (integer, optional) — The number of transactions to skip before starting to return results. Default: `0`.
* `sort` (string, optional) — The sorting order of the transactions. Possible values: `asc` (ascending) or `desc` (descending). Default: `desc`.

## Response

* `transactions` (array) — An array of transaction objects, each containing:
  * `hash` (string) — The transaction hash.
  * `lt` (string) — The logical time of the transaction.
  * `account` (string) — The account address involved in the transaction.
  * `now` (integer) — The timestamp of the transaction.
  * `origStatus` (string) — The original status of the account.
  * `endStatus` (string) — The end status of the account.
  * `totalFees` (string) — The total fees for the transaction.

## Use case

The `transactionsByMasterchainBlock` endpoint is useful for various applications that need to analyze or display transaction data for specific blocks:

1. Block explorers can use this to show all transactions included in a particular masterchain block.
2. Researchers and analysts can study transaction patterns and volumes for specific blocks.
3. Developers can use this endpoint to verify transaction inclusion in a specific block.
4. Auditing tools can track all transactions processed in a given block for compliance or security purposes.


## OpenAPI

````yaml openapi/ton_node_api/v3/getTransactionsByMasterchainBlock.json GET /transactionsByMasterchainBlock
openapi: 3.0.0
info:
  title: TON API
  version: 3.0.0
  description: API for interacting with The Open Network (TON) blockchain
servers:
  - url: >-
      https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3
security: []
paths:
  /transactionsByMasterchainBlock:
    get:
      tags:
        - Blockchain
      summary: Get Transactions by Masterchain Block
      description: Retrieves a list of transactions for a specific masterchain block
      operationId: getTransactionsByMasterchainBlock
      parameters:
        - name: seqno
          in: query
          description: The sequence number of the masterchain block
          required: true
          schema:
            type: integer
            default: 40467413
        - name: limit
          in: query
          description: The maximum number of transactions to return
          required: false
          schema:
            type: integer
            default: 128
        - name: offset
          in: query
          description: The number of transactions to skip before starting to return results
          required: false
          schema:
            type: integer
            default: 0
        - name: sort
          in: query
          description: The sorting order of the transactions
          required: false
          schema:
            type: string
            enum:
              - asc
              - desc
            default: desc
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: object
                properties:
                  transactions:
                    type: array
                    items:
                      type: object
                      properties:
                        hash:
                          type: string
                          description: The transaction hash
                        lt:
                          type: string
                          description: The logical time of the transaction
                        account:
                          type: string
                          description: The account address involved in the transaction
                        now:
                          type: integer
                          description: The timestamp of the transaction
                        origStatus:
                          type: string
                          description: The original status of the account
                        endStatus:
                          type: string
                          description: The end status of the account
                        totalFees:
                          type: string
                          description: The total fees for the transaction

````