Pending Transactions
ThependingTransactions 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 you 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
ThependingTransactions endpoint is useful for monitoring real-time transaction status:
- Wallet applications showing recently submitted transactions before full confirmation.
- Trading bots tracking order execution in real-time.
- Payment systems providing instant feedback on transaction status.
- Block explorers showing live transaction feeds.
- Monitoring systems tracking specific account activity.
Query Parameters
Filter by account address
Maximum number of transactions to return
Number of transactions to skip