Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ton-blockchain/acton/llms.txt

Use this file to discover all available pages before exploring further.

acton rpc provides fast, read-only inspection of the TON blockchain without needing a full project setup. Use it to check whether a contract is active, inspect its balance and state hashes, read the latest masterchain block, or render a complete transaction trace. When run inside an Acton project, it goes further: if the deployed contract’s code hash matches a locally compiled contract, Acton prints the matched contract name and decodes storage using the local compiler ABI.

Synopsis

acton rpc <SUBCOMMAND> [OPTIONS]

Subcommands

SubcommandDescription
infoShow account state, balance, and decoded storage
blockPrint the latest masterchain block JSON
block-numberPrint the latest masterchain block seqno
traceFetch and render a transaction trace by root hash

acton rpc info

Fetch account state for a single address and print status, balance, code/data hashes, and (when a local ABI match is found) decoded storage. Synopsis
acton rpc info <ADDRESS> [OPTIONS]
Options
FlagTypeDefaultDescription
ADDRESSstringrequiredContract address in friendly or raw format
--netstringtestnetNetwork to query: mainnet, testnet, localnet, custom:<name>
Output includes:
  • Account status (active, frozen, uninitialized)
  • Balance in TON
  • Last transaction LT and hash
  • Code hash and data hash (when the account has deployed state)
  • Matched local contract name (when a project contract has the same code_hash)
  • Decoded storage in a YAML-like view (when compiler ABI metadata is available)

acton rpc block

Print the full TonCenter getMasterchainInfo JSON response for the selected network. Synopsis
acton rpc block [OPTIONS]
Options
FlagTypeDefaultDescription
--netstringtestnetNetwork to query

acton rpc block-number

Print only the latest masterchain block seqno as a decimal number. Useful for scripting and fork configuration. Synopsis
acton rpc block-number [OPTIONS]
Options
FlagTypeDefaultDescription
--netstringtestnetNetwork to query

acton rpc trace

Fetch a TonCenter v3 trace by root transaction hash and render it using the same transaction tree formatter as acton test. Supports three verbosity levels and optional message body decoding. Synopsis
acton rpc trace <HASH> [OPTIONS]
Options
FlagTypeDefaultDescription
HASHstringrequiredRoot transaction hash (hex)
--netstringtestnetNetwork to query
--summaryflagPrint only the trace summary (conflicts with --tree, --verbose)
--treeflagPrint summary + transaction tree (default mode)
--verboseflagPrint summary, tree, and per-transaction fields
--show-bodiesflagPrint decoded message bodies in the transaction tree
Output includes:
  • Query hash and trace ID
  • Root transaction hash
  • Whether the trace is complete
  • Total transaction and message counts
  • Full transaction tree (in --tree and --verbose modes)

Network resolution

Network valueResolves to
mainnetBuilt-in TonCenter mainnet endpoint
testnetBuilt-in TonCenter testnet endpoint
localnetConfigured localnet or default http://127.0.0.1:5411
custom:<name>[networks.<name>] in Acton.toml
acton rpc does not require a project manifest for mainnet and testnet queries. For localnet and custom:<name>, Acton needs access to a project or manifest to read network configuration — use --manifest-path or --project-root when running outside the project directory.

TonCenter API keys

VariableUsed for
TONCENTER_MAINNET_API_KEY--net mainnet
TONCENTER_TESTNET_API_KEY--net testnet
<NORMALIZED_NAME>_API_KEYcustom:<name> networks
Acton loads .env automatically. Set the relevant key there for project work and use shell variables for CI or one-off overrides.

ABI matching and storage decoding

When Acton can resolve a local project, it:
  1. Fetches the remote account’s code cell
  2. Computes its code_hash
  3. Compares the hash against locally compiled contracts in Acton.toml
  4. Decodes storage with the matched contract’s compiler ABI
Storage decoding is best-effort: it works reliably for contracts you own in the current project, but is not guaranteed for arbitrary third-party deployments.

Examples

acton rpc info EQC...

Exit status

  • 0 — the selected RPC query completed successfully
  • 1 — the address was invalid, the network could not be resolved, the remote request failed, or local ABI decoding encountered an unrecoverable error

See Also

  • acton disasm (see Command Reference) — disassemble contract code fetched from the chain
  • acton retrace (see Command Reference) — replay a historical transaction locally with source-level debugging
  • acton localnet — run a local network to test against

Build docs developers (and LLMs) love