GET
/
transactionsByMasterchainBlock
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/transactionsByMasterchainBlock
{
  "transactions": [
    {
      "hash": "<string>",
      "lt": "<string>",
      "account": "<string>",
      "now": 123,
      "origStatus": "<string>",
      "endStatus": "<string>",
      "totalFees": "<string>"
    }
  ]
}

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.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

TON pricing is the same for full, archive, v2, v3

There’s no difference between a full node an archive node in data availability or pricing.
All data is always available and all node requests are consumed as 1 request unit.

​
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.

Query Parameters

​
seqno
integer
default:40467413
required

The sequence number of the masterchain block

​
limit
integer
default:128

The maximum number of transactions to return

​
offset
integer
default:0

The number of transactions to skip before starting to return results

​
sort
enum<string>
default:desc

The sorting order of the transactions

Available options:
asc,
desc

Response

200 - application/json
Successful response
​
transactions
object[]