How to inspect virtual network activity

Send requests and deployments through the Studio connection settings to capture them in API calls and the automatic contract registry.

1. Open Explorer, find an account, and inspect balances, code, storage, and transaction history. Browse blocks, jettons, and non-fungible tokens (NFTs); save useful addresses in Favorites.
2. Open a transaction to inspect phases, fees, messages, and state changes. Retrace it for execution details when matching source artifacts are available.
3. Use Contracts for registered addresses, source artifacts, and application binary interfaces (ABIs). Add existing addresses manually when their deployment did not pass through Studio. Review the Sources and ABI catalogs for available metadata.
4. Open API calls to inspect request/response data, timing, and errors. Enable the Studio requests filter to include calls made by the UI itself.

• For localnet, open Network → Health for API readiness, indexer lag, and service health. Inspect Nodes, Validators, and Stats for synchronization, elections, and queues. On startup failure, expand Diagnostic details for the runtime error. The nodes page includes Collector diagnostics for observer failures.
• The simulator has no equivalent validator or service log dashboard.

The common Studio tools provide message previews, cell inspection, address conversion, and interactive API requests.

acton simulator status --port 5411 --json
curl --fail http://127.0.0.1:5411/api/v2/getMasterchainInfo

Inspect the foreground terminal for process diagnostics. A successful status exit code can report running: false; inspect the JSON field. For pending messages, check manual mining and the virtual clock.

acton localnet status dev --json
acton localnet logs dev --tail 200

The log command prints a bounded tail of the network operation log once and exits. It does not follow a live stream. Use the reported Dashboard URL for node health and elections. For a pending operation, replace <OPERATION_ID> with its ID from status:

acton localnet operation '<OPERATION_ID>' --network dev --wait

An accepted operation is not a completed operation. Inspect its terminal status and error before using the result.