Query an account's TRX balance at a specific block after verifying that the node has recorded the required balance history.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Prerequisites and missing data
This endpoint reads balance traces stored by the node; it does not reconstruct balances from historical blocks on demand. Self-hosted nodes disable this feature by default. To use it, set storage.balance.history.lookup to true before the node processes the blocks you need. Enabling it later does not backfill earlier history.
If you do not run your own node, the official historical-balance endpoints are http://13.228.119.63:8090, http://18.139.193.235:8090, http://18.141.79.38:8090, and http://18.139.248.26:8090. Public-node availability and history coverage can change, so verify that the target block is within the recorded range before relying on a response.
If the node has no balance trace for the account at or before the requested height, java-tron may still return HTTP 200 with balance set to 0. That response cannot distinguish an actual zero balance from missing local history. For deposits, reconciliation, or audits, first verify that the node's recorded range covers the target block, using a known account or checkpoint. Do not treat 0 from an unverified data source as proof of the historical balance.
Related resources
- Accountpermissionupdate — previous in this section
- Accounts — account model
- Blocks — balance lookup by block (uses block ID)