For the complete documentation index, see llms.txt. This page is also available as Markdown.

getblocktransactionsext - TON

Example code for the getblocktransactionsext JSON-RPC method. Сomplete guide on how to use getblocktransactionsext JSON-RPC in GetBlock.io Web3 documentation.

This method returns the list of transactions in a block, with extended information for each transaction, avoiding the need for a second round trip to fetch full transaction details.

Parameters

Parameter
Type
Required
Description

workchain

integer

Yes

Workchain ID

shard

string

Yes

Shard ID as a string-encoded int64

seqno

integer

Yes

Block sequence number

root_hash

string

No

Expected root hash of the block

file_hash

string

No

Expected file hash of the block

after_lt

string

No

Logical time of the transaction to read after

after_hash

string

No

Account hash within the block, indicating the transaction to read after

count

integer

No

Maximum number of items to return (default: 40)

Request Example

REST (GET):

curl --location --request GET 'https://go.getblock.io/<ACCESS-TOKEN>/getBlockTransactionsExt?workchain=-1&shard=-9223372036854775808&seqno=45792554' \
--header 'Content-Type: application/json'

JSON-RPC (POST):

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "getBlockTransactionsExt",
    "params": {
        "workchain": -1,
        "shard": "-9223372036854775808",
        "seqno": 45792554
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

result.transactions

array

Array of full transaction objects

result.transactions[].utime

integer

Unix timestamp at which the transaction was applied

result.transactions[].fee

string

Total fee paid (nanotons)

result.transactions[].in_msg

object

Incoming message (if any)

result.transactions[].out_msgs

array

Outgoing messages

Use Cases

  • Block-by-block indexing where full transaction detail is needed

  • Avoiding the N+1 round-trips of getBlockTransactions + per-tx fetch

  • High-throughput indexers and analytics

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

422

Validation Error

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

504

Lite Server Timeout

Upstream TON liteserver timed out

SDK Integration

Last updated

Was this helpful?