Skip to main content
GET
/
pendingTransactions
Get Pending Transactions
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/pendingTransactions
{
  "transactions": [
    {
      "account": "<string>",
      "hash": "<string>",
      "lt": 123,
      "now": 123,
      "mc_block_seqno": 123,
      "trace_id": "<string>"
    }
  ],
  "address_book": {}
}

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.

​
Pending Transactions

The pendingTransactions endpoint retrieves transactions that are pending finalization in the TON blockchain. These are transactions that have been included in a block but may not yet be fully confirmed.
Get your own node endpoint todayStart 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, v3There’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

  • account (string, optional) — Filter by account address.
  • limit (integer, optional) — Maximum number of transactions to return. Default: 10.
  • offset (integer, optional) — Number of transactions to skip for pagination. Default: 0.

​
Response

  • transactions (array) — Array of pending transaction objects:
    • account (string) — Account address.
    • hash (string) — Transaction hash.
    • lt (integer) — Logical time.
    • now (integer) — Unix timestamp.
    • mc_block_seqno (integer) — Masterchain block sequence number.
    • trace_id (string) — Associated trace ID.
  • address_book (object) — Address book mapping.

​
Use case

The pendingTransactions endpoint is useful for monitoring real-time transaction status:
  1. Wallet applications showing recently submitted transactions before full confirmation.
  2. Trading bots tracking order execution in real-time.
  3. Payment systems providing instant feedback on transaction status.
  4. Block explorers showing live transaction feeds.
  5. Monitoring systems tracking specific account activity.
Here’s an example of getting pending transactions: 
curl -X GET \
  'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/pendingTransactions?limit=5' \
  -H 'accept: application/json'
Pending transactions will eventually move to the regular transactions endpoint once fully confirmed. Use this endpoint for real-time monitoring.

Query Parameters

​
account
string

Filter by account address

​
limit
integer
default:10

Maximum number of transactions to return

​
offset
integer
default:0

Number of transactions to skip

Response

200 - application/json

Successful response

​
transactions
object[]
​
address_book
object

Address book mapping

Last modified on April 15, 2026