- BlockTransactionsConnectionEdge
Represents an event emitted during the execution of a smart contract function.
Events are structured outputs generated by Pact code when certain actions occur on-chain — such as token transfers, mints, burns, or other contract-specific behaviors. They are commonly used by explorers, indexers, wallets, and analytics tools to track contract activity, monitor state changes, and trigger off-chain processes.
Each event is associated with a specific block, transaction, and request key, and includes
metadata like its qualified name (moduleName.eventName), parameters, and position within the transaction.
Globally unique identifier for this event.
The name of the event as defined in the smart contract.
Example: "TRANSFER".
The block in which this event was emitted.
The ID of the chain where the event occurred.
The height of the block in which this event was emitted.
The name of the module that emitted the event.
Example: "coin".
The index position of this event within the transaction’s event list. Useful when multiple events are emitted by the same transaction.
The request key of the transaction that emitted this event.
The raw JSON-encoded event parameters as emitted by the contract.
A human-readable text representation of the event parameters.
The fully qualified event name, combining the module and event name.
Example: "coin.TRANSFER".
The transaction that emitted this event.
Implements interfaces
A globally identifiable object in the GraphQL schema.
All core entities in this API implement the Node interface, which guarantees that they have
a unique id field, enabling consistent caching, pagination, and reference resolution across the API.
{ "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "name": "Example String", "block": { "__typename": "Block" }, "chainId": "Example Custom Scalar", "height": "Example Custom Scalar", "moduleName": "Example String", "orderIndex": "Example Custom Scalar", "requestKey": "Example String", "parameters": "Example String", "parameterText": "Example String", "qualifiedName": "Example String", "transaction": { "__typename": "Transaction" } }
Represents a fungible account on a specific chain in the Kadena blockchain.
While a FungibleAccount aggregates balances and activity across all chains, a FungibleChainAccount
focuses on a single chain. It exposes the account’s balance, security guard, and full transaction
and transfer history specific to that chain and fungible token (e.g., coin for KDA).
This type is useful when you need fine-grained, chain-level data — such as for explorers, wallets, or analytics tools that track balances and movements per chain.
Globally unique identifier for this chain account node.
The full name of the account (e.g., k:abcdef123456... for a user account or free.my-contract for a contract account).
The current balance of this account on the specified chain for the given fungible token.
The chain ID where this account exists.
The name of the fungible token module associated with this account (e.g., coin).
The guard that defines the account’s security conditions. A guard determines who must sign transactions in order to spend from this account.
Paginated list of transactions involving this account on this chain. Transactions represent operations such as transfers, contract calls, or other state changes.
Paginated list of token transfers into or out of this account on this chain. Transfers are a subset of events focused specifically on balance movements.
Implements interfaces
A globally identifiable object in the GraphQL schema.
All core entities in this API implement the Node interface, which guarantees that they have
a unique id field, enabling consistent caching, pagination, and reference resolution across the API.
{ "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "accountName": "Example String", "balance": 40, "chainId": "Example String", "fungibleName": "Example String", "guard": { "__typename": "IGuard" }, "transactions": { "__typename": "FungibleChainAccountTransactionsConnection" }, "transfers": { "__typename": "FungibleChainAccountTransfersConnection" } }
{ "edges": [ { "cursor": "Example String", "node": { "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "cmd": { "__typename": "TransactionCommand" }, "hash": "Example String", "result": { "__typename": "TransactionMempoolInfo" }, "sigs": [ { "__typename": "TransactionSignature" } ] } } ], "pageInfo": { "startCursor": "Example String", "endCursor": "Example String", "hasNextPage": true, "hasPreviousPage": true }, "totalCount": 40 }
{ "cursor": "Example String", "node": { "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "cmd": { "__typename": "TransactionCommand" }, "hash": "Example String", "result": { "__typename": "TransactionMempoolInfo" }, "sigs": [ { "__typename": "TransactionSignature" } ] } }
{ "edges": [ { "cursor": "Example String", "node": { "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "cmd": { "__typename": "TransactionCommand" }, "hash": "Example String", "result": { "__typename": "TransactionMempoolInfo" }, "sigs": [ { "__typename": "TransactionSignature" } ] } } ], "pageInfo": { "startCursor": "Example String", "endCursor": "Example String", "hasNextPage": true, "hasPreviousPage": true }, "totalCount": 40 }
{ "cursor": "Example String", "node": { "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "cmd": { "__typename": "TransactionCommand" }, "hash": "Example String", "result": { "__typename": "TransactionMempoolInfo" }, "sigs": [ { "__typename": "TransactionSignature" } ] } }
Represents a transaction executed on the Kadena blockchain.
A Transaction encapsulates the full structure and outcome of a blockchain transaction —
from the original signed command to the resulting execution details.
Each transaction is uniquely identified by its hash and includes the submitted command (cmd),
associated signatures (sigs), and the execution result (result).
This type is fundamental for querying and analyzing blockchain activity, tracking execution outcomes, and verifying signed payloads.
Globally unique identifier for this transaction node.
The original signed transaction command submitted to the network. Includes metadata, payload, signers, and network information.
The unique hash of the transaction. This value is derived from the signed command and serves as the canonical identifier for the transaction on-chain.
The result of executing the transaction. Includes information such as success/failure status, events, continuation data, and any state changes triggered by execution.
The list of signatures associated with the transaction. Each signature proves authorization from a required signer and is used to validate that the transaction was properly authorized before execution.
Implements interfaces
A globally identifiable object in the GraphQL schema.
All core entities in this API implement the Node interface, which guarantees that they have
a unique id field, enabling consistent caching, pagination, and reference resolution across the API.
{ "id": "9cfb1c81-4c79-452f-b1f5-8ee6571276b4", "cmd": { "__typename": "TransactionCommand" }, "hash": "Example String", "result": { "__typename": "TransactionMempoolInfo" }, "sigs": [ { "__typename": "TransactionSignature" } ] }
Represents the full command structure of a transaction on the Kadena blockchain.
A TransactionCommand defines all the inputs required to construct and execute
a Pact transaction, including metadata, payload, signers, and supporting information.
It reflects the exact structure submitted to the blockchain for validation and execution.
Transaction-level metadata, such as gas price, gas limit, chain ID, time-to-live (TTL), and creation time. This controls how and when the transaction is processed by the chain.
The network identifier where the transaction is intended to run.
Example: "mainnet01" or "testnet04".
A user-specified nonce string that ensures transaction uniqueness. Typically includes random or timestamp data to prevent replay.
The payload of the transaction, which defines the Pact code to execute or the continuation to resume. This is the core logic being invoked.
The list of signers required to authorize the transaction. Each signer specifies a public key and associated capabilities that define what actions they are permitted to authorize.
{ "meta": { "__typename": "TransactionMeta" }, "networkId": "Example String", "nonce": "Example String", "payload": { "__typename": "ContinuationPayload" }, "signers": [ { "__typename": "Signer" } ] }
Execution metadata that defines how a transaction is processed on the Kadena blockchain.
TransactionMeta contains contextual information that influences transaction execution,
such as which chain it runs on, how long it remains valid, its gas configuration, and
when it was created. This data is included in every TransactionCommand and is critical
for determining how the transaction is validated and scheduled by the network.
The ID of the chain where the transaction will be executed.
The timestamp when the transaction was created. Used by the network to validate transaction age and enforce time-to-live rules.
The maximum amount of gas units the transaction is allowed to consume during execution. Acts as a safety limit to prevent excessive gas usage.
The price (in KDA) to pay per unit of gas.
Determines the total transaction fee when multiplied by gasLimit.
The account name of the sender responsible for paying gas fees.
The time-to-live (TTL) of the transaction, expressed in seconds.
It defines how long the transaction remains valid after its creationTime.
Once this period passes, the transaction expires and will no longer be accepted.
{ "chainId": "Example Custom Scalar", "creationTime": "Example Custom Scalar", "gasLimit": "Example Custom Scalar", "gasPrice": "Example String", "sender": "Example String", "ttl": "Example Custom Scalar" }
List of capabilities associated with/installed by this signer.
{ "sig": "Example String" }
The payload of an cont transaction.
The environment data made available to the transaction. Formatted as raw JSON.
A unique id when a pact (defpact) is initiated. See the "Pact execution scope and pact-id" explanation in the docs for more information.
The proof provided to continue the cross-chain transaction.
Whether or not this transaction can be rolled back.
The step-number when this is an execution of a defpact, aka multi-step transaction.
{ "data": "Example String", "pactId": "Example String", "proof": "Example String", "rollback": true, "step": 40 }