Skip to main content
GET
/
events
Get Events
curl --request GET \
  --url https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/events
{
  "events": [
    {
      "trace_id": "<string>",
      "external_hash": "<string>",
      "mc_seqno_start": "<string>",
      "mc_seqno_end": "<string>",
      "start_lt": "<string>",
      "start_utime": 123,
      "end_lt": "<string>",
      "end_utime": 123,
      "trace_info": {},
      "actions": "<array>",
      "is_incomplete": true
    }
  ],
  "address_book": {}
}

​
Events

The events endpoint queries blockchain events, which combine traces with their decoded actions. Events provide a complete view of what happened in a transaction flow, including all resulting actions.
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.
  • start_utime (integer, optional) — Start of time range (unix timestamp).
  • end_utime (integer, optional) — End of time range (unix timestamp).
  • limit (integer, optional) — Maximum number of events to return. Default: 10.
  • offset (integer, optional) — Number of events to skip for pagination. Default: 0.
  • sort (string, optional) — Sort order: asc or desc. Default: desc.

​
Response

  • events (array) — Array of event objects:
    • trace_id (string) — Trace ID.
    • external_hash (string) — Hash of the external message.
    • mc_seqno_start (string) — Start masterchain sequence number.
    • mc_seqno_end (string) — End masterchain sequence number.
    • start_lt (string) — Start logical time.
    • start_utime (integer) — Start unix timestamp.
    • end_lt (string) — End logical time.
    • end_utime (integer) — End unix timestamp.
    • trace_info (object) — Trace state and statistics.
    • actions (array) — Decoded actions from the event.
    • is_incomplete (boolean) — Whether the event is still processing.
  • address_book (object) — Address book mapping.

​
Use case

The events endpoint is useful for applications that need combined trace and action data:
  1. Building activity feeds showing user transaction history.
  2. Notification systems alerting on specific events.
  3. Analytics dashboards tracking blockchain activity.
  4. Block explorers showing transaction details with decoded actions.
  5. Debugging complex multi-contract interactions.
Here’s an example of getting recent events: 
curl -X GET \
  'https://ton-mainnet.core.chainstack.com/f2a2411bce1e54a2658f2710cd7969c3/api/v3/events?limit=5' \
  -H 'accept: application/json'
Events combine the structure of traces with the decoded information from actions, making them ideal for building user-facing transaction histories.

Query Parameters

​
account
string

Filter by account address

​
start_utime
integer

Start of time range (unix timestamp)

​
end_utime
integer

End of time range (unix timestamp)

​
limit
integer
default:10

Maximum number of events to return

​
offset
integer
default:0

Number of events to skip

​
sort
enum<string>
default:desc

Sort order

Available options:
asc,
desc

Response

200 - application/json

Successful response

​
events
object[]
​
address_book
object

Address book mapping