ton

Tables

Jetton_Burn_event

Jetton token burn events on TON blockchain, recording token destruction from specific jetton wallets with amounts, source addresses, and associated jetton master contracts. Used for tracking token supply reduction and analyzing deflationary tokenomics across TON’s fungible token standard.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, millisecond precision.
`type`	`STRING`	Event type identifier for TON jetton operations, always set to “burn” for this table. Indicates the destruction of jetton tokens from circulation.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`transaction_logical_time`	`INT64`	Logical time sequence number assigned by TON blockchain to order transactions within and across blocks. Used for precise transaction ordering and causal relationship tracking on TON network.
`trace_id`	`STRING`	Unique identifier for a transaction trace or execution path within the blockchain. Base64-encoded string for TON chains, prefixed format for EVM chains.
`transaction_aborted`	`BOOL`	Indicates whether the transaction containing this burn event was aborted and did not complete successfully. True when the transaction failed, false when it executed normally.
`query_id`	`BIGNUMERIC`	Unique identifier for this specific jetton burn request, used to track and correlate the burn operation across the TON network. Typically a large integer value assigned by the requesting contract.
`amount`	`BIGNUMERIC`	Quantity of tokens involved in the transaction. Integer value representing the smallest denomination of the token.
`source`	`STRING`	Address or identifier of the entity that initiated or originated the transaction or event.
`destination`	`STRING`	Recipient address that receives notification or value after the burn operation completes. Typically null or addr_none in TON Jetton burn events, as burned tokens are destroyed rather than transferred.
`jetton_wallet`	`STRING`	TON blockchain address of the jetton wallet contract that holds the token balance for a specific owner. Represented as workchain:hash format (e.g., 0:68D6…) following TON address standards.
`jetton_master`	`STRING`	Contract address of the jetton (TON token standard) master contract that governs this token. Represents the canonical token identifier on TON, formatted as a colon-separated workchain:hash address.
`response_destination`	`STRING`	TON address designated to receive excess gas and notification responses from the burn operation. Typically set to `addr_none` when no response handling is required.
`custom_payload`	`BYTES`	Optional binary data attached to the burn operation, allowing custom application-specific information to be passed with the transaction. Typically null in standard jetton burns, as evidenced by sample data.
`forward_ton_amount`	`BIGNUMERIC`	Amount of TON cryptocurrency to be forwarded with the burn notification, specified in nanotons (1 TON = 10^9 nanotons). Null when no TON forwarding is requested with the burn operation.
`forward_payload`	`BYTES`	Optional arbitrary data forwarded to the response destination address after the burn operation. Typically null, as most jetton burn transactions do not include additional payload for forwarding.
`comment`	`STRING`	User-provided text annotation or memo attached to the burn transaction. Typically null, but may contain arbitrary string data when specified by the sender.

Sample Data

type	amount	source	query_id	trace_id	jetton_master	jetton_wallet	block_timestamp	transaction_hash	transaction_aborted	response_destination	transaction_logical_time
burn	400000000000	0:4398C8253C89D3BBC7EFB9D5CA8F2BBEAD3CDA485D03B9A499011A99E6681642	7901652718239168512	x9WNShB+Gv2enT1XeOEdjIvzz/uJWLpDn+DHu1RFBR0=	0:0034190C3F1920F9020655679D7109A75450F87DB8ABF676E9587D767BEA17C2	0:68D6152BBB8714B1A862932A3595D41B664570DC247DE87375F0B7A5D8F32C99	2024-04-02T09:51:54.000Z	x4J2A3XNVYirXozb7CxLuLslShJW3pDyklaRkz2Z0X8=	false	addr_none	45627342000003
burn	206287978037	0:9C61CF6DB91553B6E8BA5D6F5DC082FE321FC38D31D591E0CD34149492D35F92	12531509142989699072	BobF6BRjrgE/u45EUeebB/gjGIOqbK32aUHajwUNM00=	0:011E4C677529EAAC180C20347BDCB0741410C33340BF529DFD10BD519F76A8FF	0:D84FF926C7522919E471DA60255A3E35F29F44BB45F5DEDAD26D837FEA31E750	2024-04-02T20:04:55.000Z	WtaOQWAccxbaBeRmclQYVT7JwEdL6KtsgDdXmnkFoo4=	false	addr_none	45635291000003
burn	216791170580	0:0658819032A8F05E36ACFAB393A5F7E6F6D3B52B51B0D1BFC1A84C4E3A933A82	7262520106926527488	58UVO3+IWbeeU5htw4bXa/x7rkxq6O1R0aeLeqobEmg=	0:011E4C677529EAAC180C20347BDCB0741410C33340BF529DFD10BD519F76A8FF	0:5F927833885A8E778C58F5861CAFB84C3DB28A86763179A1E8BADB149CA41607	2024-04-02T13:51:30.000Z	v3imoZ8l+eaW9H9wfd+d+txBklKkB3EtY6Wsr870Lw8=	false	addr_none	45630482000003

Example Query

Query with partition filter

SELECT *
FROM `tt-contracts.ton.Jetton_Burn_event`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

Jetton_Mint_event

Jetton token minting events on TON blockchain, recording new token issuance with amounts, recipient wallets, and jetton master contract addresses. Used for tracking token supply changes, analyzing minting patterns, and monitoring jetton (TON’s fungible token standard) distribution activity.

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, millisecond precision.
`type`	`STRING`	Event type identifier indicating the operation performed. Always set to “mint” for this table, representing jetton token creation events on TON blockchain.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`transaction_logical_time`	`INT64`	Monotonically increasing logical timestamp assigned to each transaction on TON blockchain. Used for ordering transactions within blocks and across the network.
`trace_id`	`STRING`	Unique identifier for a transaction trace or execution path within the blockchain. Base64-encoded string for TON chains, prefixed format for EVM chains.
`transaction_aborted`	`BOOL`	Transaction execution status indicating whether the mint operation failed or was aborted on-chain. Always false in these samples, meaning successful mint completions.
`query_id`	`BIGNUMERIC`	Application-level identifier for tracking the mint operation, typically set by the calling contract. Usually 0 for simple mints, but can be used to correlate requests and responses in complex workflows.
`amount`	`BIGNUMERIC`	Quantity of tokens involved in the transaction. Integer value representing the smallest denomination of the token.
`source`	`STRING`	Address or identifier of the entity that initiated or originated the transaction or event.
`destination`	`STRING`	Address of the wallet receiving the newly minted jetton tokens on TON. Formatted as workchain:address in hex (e.g., 0:416414EF…).
`jetton_wallet`	`STRING`	Contract address of the jetton wallet that received the minted tokens on TON blockchain. Represented as workchain:address format (e.g., 0:F56073D4127C3F98…).
`jetton_master`	`STRING`	Address of the Jetton master contract that controls the minting and overall configuration of this token. All mint events for a specific token will share the same jetton_master address.
`response_destination`	`STRING`	Destination address where excess TON from the mint operation should be returned. Typically null, as mint operations usually do not generate excess funds requiring return.
`custom_payload`	`BYTES`	Custom payload data optionally included in the mint operation, typically used to pass additional parameters to the minting contract. Rarely populated, as seen in sample data where most values are null.
`forward_ton_amount`	`BIGNUMERIC`	Amount of TON cryptocurrency to be forwarded along with the minted jetton tokens, denominated in nanotons (1 TON = 1 billion nanotons). Often zero when no TON forwarding is required with the mint operation.
`forward_payload`	`BYTES`	Binary data passed along with the mint operation, typically containing encoded instructions or metadata for the receiving contract. Often null or contains structured bytes for inter-contract messaging on TON.
`comment`	`STRING`	Optional text message or memo attached to the mint operation. Typically empty or null, as seen in most transactions where users don’t include descriptive comments.

Sample Data

type	amount	trace_id	destination	jetton_master	jetton_wallet	block_timestamp	forward_payload	transaction_hash	forward_ton_amount	transaction_aborted	transaction_logical_time
mint	4980490205	aukzbchZ0Y6Dj9ZZTHsXv2h+cAK83JtmN+ehTv8nC5w=	0:416414EF7F73FD8590C7D9B6F564028A04983D72A580B252635513800AF9D67E	0:CF76AF318C0872B58A9F1925FC29C156211782B9FB01F56760D292E56123BF87	0:F56073D4127C3F98ACF85888269B32892325D32A7F3DE07C2CBC4CB1A14C0B83	2024-07-22T08:11:00.000Z		fIOu1orBigik8ZdLPnjnTy90/Hj4usAGpVlwe36OJuk=		false	47926886000005
mint	1000000000000000000	g38QnmLbVoWbRhDwkPJhxpR3hY+p3bOm5Bx/O/9MebU=	0:64EB403FEF5D2219B8D41A37042D570B0D86976BCAD6B4CD387AF681AA7B37B0	0:877078DF7DAE07A37590A759D76570381BD1AFF6C672CCBF32F18858E1548F8A	0:F7B55DBDCBDCF76B8F72B56A867C7AF9A6CF41613B8B843925A43E5CA216CD11	2024-07-22T16:24:18.000Z	{“data”:[181,238,156,114,193,1,1,1,0,2,0,2,0,0,184,1,248,107],“type”:“Buffer”}	roG0zbYZa2ukSCgKbr1LyMLYbISoGPYQTNfxxhk5t0Y=	10000000	false	47934779000007
mint	71510440095	1Jqm58n/Q20TXrXpcfTMGLfaK4uK5Kook/0APzoNPaA=	0:C64BA40185B05F96FB165490915A400D331973BF83296C5729F0F05EC8997767	0:CD0EFE78BFF4C4539B76EAB17293296C74F42CBF99EC499687FEFEC94893ED32	0:2F8108566E77F95C17AD660F94E03E0C598556CAEF207BE4358581E49C236E71	2024-07-22T03:19:50.000Z	{“data”:[181,238,156,114,193,1,1,1,0,36,0,36,0,67,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,64,21,227,154,164],“type”:“Buffer”}	ScRBjAJ1v7k6CHno7PqPMcRfY3WyeF1g+DFbqGTHlH4=	0	false	47921926000013

Example Query

Query with partition filter

SELECT *
FROM `tt-contracts.ton.Jetton_Mint_event`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

Jetton_Transfer_event

Jetton token transfer events on TON blockchain, tracking token movements between wallets with amounts, sender/receiver addresses, and optional message comments. Used for analyzing token flows, transaction patterns, and DeFi activity across TON’s jetton standard (similar to ERC-20).

Columns

Column	Type	Description
`block_timestamp`	`TIMESTAMP`	Timestamp when the block was produced. UTC timezone, millisecond precision.
`type`	`STRING`	Event type identifier for the Jetton transfer operation. Always contains the value “transfer” for records in this table.
`transaction_hash`	`STRING`	Unique identifier for the transaction. 66-character hex string including 0x prefix.
`transaction_logical_time`	`INT64`	Monotonically increasing logical timestamp representing the transaction’s position in the TON blockchain sequence. Higher values indicate later transactions, used for ordering events within the network.
`trace_id`	`STRING`	Unique identifier for a transaction trace or execution path within the blockchain. Base64-encoded string for TON chains, prefixed format for EVM chains.
`transaction_aborted`	`BOOL`	Boolean flag indicating whether the transaction containing this transfer event failed or was reverted. False means successful execution, true means the transaction was aborted.
`query_id`	`BIGNUMERIC`	Unique identifier for this jetton transfer operation assigned by the sender. Typically represented as a large integer and may be used for deduplication or tracking transfer requests.
`amount`	`BIGNUMERIC`	Quantity of tokens involved in the transaction. Integer value representing the smallest denomination of the token.
`source`	`STRING`	Address or identifier of the entity that initiated or originated the transaction or event.
`destination`	`STRING`	Recipient address of the jetton transfer on TON blockchain. Hex-encoded, 0x-prefixed address identifying the wallet or contract receiving the tokens.
`jetton_wallet`	`STRING`	Contract address of the jetton wallet that executed this transfer on the TON blockchain. Hex-encoded, 0x-prefixed identifier representing the sender’s wallet contract for the specific jetton token.
`jetton_master`	`STRING`	Address of the Jetton master contract that defines the token being transferred. Acts as the token’s unique identifier on TON blockchain, similar to an ERC-20 contract address.
`response_destination`	`STRING`	TON address where excess gas fees and notifications should be sent after the transfer completes. Typically set to the sender’s address to receive unused funds from the transaction.
`custom_payload`	`BYTES`	Optional binary data field for custom application-specific payloads in Jetton transfers. Null in most standard transfers; when present, contains protocol-specific encoded data for advanced transfer logic.
`forward_ton_amount`	`BIGNUMERIC`	Amount of TON (in nanotons) forwarded with the transfer for notification or callback purposes. Often set to 1 nanoton for minimal notification or higher amounts to cover gas for complex operations.
`forward_payload`	`BYTES`	Binary data passed along with the transfer for application-specific logic or cross-contract messaging. Often contains encoded instructions for DeFi protocols, DEX operations, or smart contract interactions on TON.
`comment`	`STRING`	Optional text message attached to the transfer, encoded as a UTF-8 string. Commonly contains reference numbers, notes, or may be null when no comment is provided.

Sample Data

type	amount	source	comment	query_id	trace_id	destination	jetton_master	jetton_wallet	custom_payload	block_timestamp	forward_payload	transaction_hash	forward_ton_amount	transaction_aborted	response_destination	transaction_logical_time
transfer	58027828923177	0:0472E7AF7D3C2A7395F2116D14640285B7E147343DC068203341E5240CA8CF3F		6800441507717217280	rw0HoHKBOB+5ihwLM5Rpo/pTT/buRa9OQXbWkRy8OE4=	0:3CEC7DA8613F505B68D4AA5D4A0598432EDDD4BEC8437C68380AF4DFBCC016F8	0:905737D037268C177108EAED19B7B51672DEAEE90545DE7FA73D406ED07AA979	0:00011874CBA35953614C789AFFD01F063FF8C548803CDA5179DFF54BF2F60E03		2024-06-27T18:42:49.000Z	{“data”:[181,238,156,114,65,1,2,1,0,119,0,1,85,227,160,212,130,128,11,73,36,226,103,146,216,32,231,9,21,70,235,61,248,131,119,27,132,162,112,71,250,29,233,132,38,3,96,53,19,122,68,98,33,87,162,64,1,0,142,0,0,0,0,128,0,142,92,245,239,167,133,78,114,190,66,45,162,140,128,80,182,252,40,230,135,184,13,4,6,104,60,164,129,149,25,231,240,3,235,12,253,82,147,216,159,207,142,221,120,152,28,195,125,230,169,83,245,172,90,26,252,96,152,21,220,67,234,228,90,164,126,85,153,36],“type”:“Buffer”}	rJ2sYbgA9VcyGtMdYsHatGHp0T/jj+GD+Bmc22Mn/8s=	250000000	false	0:0472E7AF7D3C2A7395F2116D14640285B7E147343DC068203341E5240CA8CF3F	47374646000003
transfer	10000000000	0:A884009C5ACAF9B5A5EB2A0F1C1D204623893D3DF7BDEFC13A82749E13C557E9	”Wake up, happy owner of the utilitarian NFT Runeston!
I, just like you, received my NFT absolutely for free. You can easily check this and make sure that Runeston is an active project!
Just go to the project channel and learn everything about Runeston!“	6083770390251875328	4/MnVwUCtqCwR1ulDokApOOihDnHB61hIleIDoSnbRU=	0:2A86A5194FBF08B19232FBAECA0016230507252BABEE3D33FCB22C32D776EAF7	0:A2821D07C97169A021677CA43223C8D610AECA85B12C3A93058E8DE051124A3B	0:0005E08F24A7D177CE05BE58062F42BEA83CD94C102D24A1DC1589AFE0D9EAC8		2024-06-27T15:32:34.000Z	{“data”:[181,238,156,114,65,2,3,1,0,1,12,0,1,254,0,0,0,0,34,87,97,107,101,32,117,112,44,32,104,97,112,112,121,32,111,119,110,101,114,32,111,102,32,116,104,101,32,117,116,105,108,105,116,97,114,105,97,110,32,78,70,84,32,82,117,110,101,115,116,111,110,33,10,32,73,44,32,106,117,115,116,32,108,105,107,101,32,121,111,117,44,32,114,101,99,101,105,118,101,100,32,109,121,32,78,70,84,32,97,98,115,111,108,117,116,101,108,121,32,102,111,114,32,102,114,101,101,46,32,89,111,117,32,99,97,110,32,101,97,115,105,1,1,254,108,121,32,99,104,101,99,107,32,116,104,105,115,32,97,110,100,32,109,97,107,101,32,115,117,114,101,32,116,104,97,116,32,82,117,110,101,115,116,111,110,32,105,115,32,97,110,32,97,99,116,105,118,101,32,112,114,111,106,101,99,116,33,32,10,74,117,115,116,32,103,111,32,116,111,32,116,104,101,32,112,114,111,106,101,99,116,32,99,104,97,110,110,101,108,32,97,110,100,32,108,101,97,114,110,32,101,118,101,114,121,116,104,105,110,103,32,97,98,111,117,116,32,82,117,110,101,2,0,12,115,116,111,110,33,34,162,53,71,225],“type”:“Buffer”}	k6M9efFAHZAaUilQssl4guwNkUvpp3F3X5L9JK76g3k=	1	false	0:A884009C5ACAF9B5A5EB2A0F1C1D204623893D3DF7BDEFC13A82749E13C557E9	47371964000001
transfer	1735000000000	0:637F75E9006CECFE2338792A31F3807724DB093430FC7781D509746BB6A81DCD		6083770387524059136	+TEeeTDTO5FYgHKo42lXGmUF8RTAojWWFw+iOvRoFU8=	0:1065449864D63DAD036C296FA22A782B43AA52F7496934333919BE38FFFC4218	0:2F956143C461769579BAEF2E32CC2D7BC18283F40D20BB03E432CD603AC33FFC	0:0009CC030666DCB276EFE13349E26D65903296CC51F5BE9A2C27C6914A9F9693		2024-06-27T00:48:30.000Z		35x6Y4lXP7YWFvkqDvsXGaRoR+1xTIoSIzMoUgM6oVY=	1	false	0:637F75E9006CECFE2338792A31F3807724DB093430FC7781D509746BB6A81DCD	47358992000003

Example Query

Query with partition filter

SELECT *
FROM `tt-contracts.ton.Jetton_Transfer_event`
WHERE block_timestamp >= DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY)
LIMIT 100

Overview

Metrics

Primitives

Contracts

Blockchain

Tables

Jetton_Burn_event

Jetton_Mint_event

Jetton_Transfer_event

​Tables

​Jetton_Burn_event

​Jetton_Mint_event

​Jetton_Transfer_event

Tables

Jetton_Burn_event

Jetton_Mint_event

Jetton_Transfer_event