Dash Tx Flow
dash_tx_flowFull flow of one or several Dash (dash, DASH, mainnet) transactions: all INPUT addresses (senders) and OUTPUT addresses (receivers) with amounts, each annotated. Note is unknown on nearly every Dash output — change is not detected, so any output can be the payment. THE hop primitive for DASH tracing: follow a recipient to its own spends (dash_sent_from_address) and repeat. tx_hash is the 64-hex id as returned by the other dash tools; pass several ids separated by "|" (up to 50; ids past the 50th are ignored) to expand a batch in one call — the Tx column attributes each row. Side is input, output, fee (the miner fee of the transaction — one row per transaction, 0 on a block reward) or not_found (a requested id that does not exist here — check the id and the chain). Index is the position of the input or output inside the transaction, and Funded_By_Tx on an input row is the transaction that created the coins being spent — pass it back to this tool to trace one hop backwards. An output whose address is also one of the transaction's OWN input addresses is marked change_to_input_address: the wallet paid itself, so it is not a payment to someone else. Outputs whose script has no standard address carry a placeholder instead of an address: m-… (a bare multisig script) or d-… (a data or other non-standard script; one d-… value can stand for many unrelated outputs). A placeholder cannot be looked up with the address tools — the visible trail ends there. Change detection is not available on Dash: no output is classified as change (nearly every Note is unknown), so the change a wallet pays to another of its own addresses counts as a payment - Targets, Top_Receivers and tx_flow outputs can include such change. Outputs back to the address itself are still left out; dash_related_addresses shows likely same-owner addresses, and dash_tx_flow marks an output paid back to one of the transaction's own input addresses as change_to_input_address, which is the only change signal Dash has. Address labels are not available for this chain, so exchange / mixer / service nodes cannot be recognized from this data.
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": {
"tx_hash": "<tx_hash>"
},
"name": "dash_tx_flow"
}
}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 |
| tx_hash | Yes | Dash transaction id, 64-hex (as shown by the other dash tools). Several ids may be passed separated by "|". Anything that is not a 64-character hex id is refused. Up to 50 are read. |