wallet-cli tx status¶

Show confirmation status of a transaction.

Synopsis¶

wallet-cli tx status --txid <id> [options]

Description¶

Reports which step a transaction is at, using four states, on TRON and EVM networks alike. After sending, scripts and agents poll it to learn whether the tx made it on-chain and succeeded. These four state values are stable — they won't be renamed or dropped across versions — so you can program against them (see the wallet-cli.result.v1 output contract in machine-interface).

`data.state`	Meaning	Terminal?
`confirmed`	Included in a block and an execution result/receipt is available; `blockNumber` present	yes
`failed`	Included and reverted / rejected	yes
`pending`	Seen by the node, with no execution result/receipt yet	no — keep polling
`not_found`	Unknown to the queried endpoint (wrong network, not propagated, dropped, or pruned); outcome unknown	no — keep polling/reconcile; do not assume failure

confirmed is an inclusion-and-receipt state, not a finality guarantee. If a workflow needs finality, verify it separately with a TRON SolidityNode view or an EVM finalized block.

Options¶

Option	Description
`--txid <string>`	Required. Transaction id/hash — bare hex on TRON, `0x…` on EVM

Plus the global options.

Examples¶

wallet-cli tx status --txid 34d9da372cd7fa9d4e7384744c0925af9d682eef4c9410fb831e0b87b355171b --network tron:3448148188

TxID           34d9da372cd7fa9d4e7384744c0925af9d682eef4c9410fb831e0b87b355171b
Status         confirmed ✅
Block          #70,433,563
Confirmations  1

{"schema":"wallet-cli.result.v1","success":true,"command":"tx.status","data":{"txid":"34d9da372cd7fa9d4e7384744c0925af9d682eef4c9410fb831e0b87b355171b","state":"confirmed","confirmed":true,"failed":false,"blockNumber":70433563,"confirmations":1},"meta":{"durationMs":732,"warnings":[]},"chain":{"family":"tron","network":"tron:3448148188","chainId":"3448148188"}}

The same query on an EVM network, by 0x hash:

wallet-cli tx status --txid 0x55b0068ef31bce39bbf5b06d456eaef307fd77f96d85ea291f48c1ae4b900d80 --network eip155:11155111 -o json

{"schema":"wallet-cli.result.v1","success":true,"command":"tx.status","data":{"txid":"0x55b0068ef31bce39bbf5b06d456eaef307fd77f96d85ea291f48c1ae4b900d80","state":"confirmed","confirmed":true,"failed":false,"blockNumber":11576586,"confirmations":0},"meta":{"durationMs":408,"warnings":[]},"chain":{"family":"evm","network":"eip155:11155111","chainId":"11155111"}}

An unknown txid is a success with state: "not_found" (exit 0) — the query worked; this endpoint has no record of that hash:

{"schema":"wallet-cli.result.v1","success":true,"command":"tx.status","data":{"txid":"0000…0000","state":"not_found","confirmed":false,"failed":false},"meta":{"durationMs":1022,"warnings":[]},"chain":{"family":"tron","network":"tron:3448148188","chainId":"3448148188"}}

On EVM, not_found also carries a meta.warnings entry, because a public endpoint that has pruned its history is indistinguishable from a hash that never existed:

{"…":"…","data":{"txid":"0x0000…0000","state":"not_found","confirmed":false,"failed":false},"meta":{"durationMs":407,"warnings":["0x0000…0000 is unknown to this endpoint. Public nodes often prune history, so this may mean the node has no record of it rather than that it never existed; try an archival endpoint."]}}

A polling deadline that ends in pending or not_found is still an unknown outcome. Do not treat it as failure or use it as an automatic resend trigger; reconcile the txid against the intended network and endpoint history first.

Output¶

Field	Type	Meaning
`txid`	string	Echo of the queried id
`state`	string	`confirmed` / `failed` / `pending` / `not_found`
`confirmed` / `failed`	boolean	Direct-branch conveniences mirroring `state`
`blockNumber`	number	Present when confirmed
`confirmations`	number	Blocks on top of the including block; present when confirmed

Exit status¶

0 query answered (including not_found) · 1 execution failure (node unreachable, timeout) · 2 usage error.