Tron Trace Dominant Path
tron_trace_dominant_pathAUTO-WALK the dominant (largest-total-amount) OUTGOING edge of ONE token from a
Tron (trx, TRX, TRON) address, hop by hop, up to 5 hops — collapses ~5 manual
tron_trace_next_hop calls into one. Every hop returns Hop*_To (the address that
received), Hop*_Token (the contract of the token that moved) and Hop*_Edge_Total, plus
Hops_Found (how many hops resolved) and Path_Status for the walk itself.
Hop*_Edge_Total is NOT the amount that travelled along the path: it is the ALL-TIME
total of EVERY transfer of that token between that hop's sender and receiver, so it
can be orders of magnitude larger than the sum you are tracing and the hop totals are
not comparable with each other. To break one edge down — its transfer count
(Transfers), first/last seen, and the full ranking of that address's edges — call
tron_trace_next_hop on the hop's sender.
The walk NEVER goes back to an address it has already visited (the seed included), so
it cannot bounce back and forth between the same two wallets — each hop is the largest
edge to a NEW address.
READ Path_Status FIRST — NO_MATCH means the token filter matched nothing (wrong symbol,
or that symbol belongs to a different token — pass contract), PATH_END means the
trail really ran out, DEPTH_LIMIT means it may continue past hop 5. All-NULL hops with
NO_MATCH are a filter problem, not a dead end.
Pass the hop addresses to labels_for_addresses and read down to the FIRST labeled
address (CEX / service) — that's the destination.
Pin the token with contract whenever you know it — a SYMBOL is not unique, clone
tokens reuse popular symbols, and with a symbol alone the hops can drift between
look-alike tokens; compare the per-hop token contract to spot that.
LIMITS: follows only the single biggest edge per hop (misses splits / fan-outs), fixed
depth 5, and transfers to the burn address are not followed. For branching / adaptive
tracing call tron_trace_next_hop hop by hop, identify each hop with
labels_for_addresses and choose the next address yourself (prompt_playbook with
playbook=money_flow returns the full step-by-step procedure); for one hop's full ranking use
tron_trace_next_hop. Heavy multi-hop walk — can time out on a very busy address; retry,
or narrow it with contract / a less-busy token.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"address": "<address>",
"currency": "<currency>"
},
"name": "tron_trace_dominant_path"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Shape of the returned data. "rows" (the default) returns one item per row. "columnar" returns a single item, {"columns":[...],"rows":[[value,...],...]}, naming the columns once and listing each row's values in that order; it is more compact for large results and carries the same values. | rows |
| address | Yes | Seed Tron base58 address (T...). | |
| contract | No | Restrict the walk to ONE exact token by its contract address (base58, starts with T) — the reliable way to pin a token, since a symbol also matches clone tokens. Overrides `currency` when both are given. Empty = follow `currency` instead. | |
| currency | Yes | Token symbol to follow, e.g. "USDT", "TRX". Ignored when `contract` is given. A symbol is NOT unique — clone tokens reuse popular symbols, so prefer `contract` when you have it. No backslashes. |