Release v1.1.11
Feature
- Added
-e, --onlyToken
option to value transfer diagrams for just token transfers.debug_traceTransaction
is not required of the node provider. The downside is ETH transfers are not included. - Added network to bottom of value transfer diagrams. eg mainnet, polygon.
- For each transaction, add network, block and time at the bottom when there are multiple transactions.
Fixes
- Value transfer diagrams from chains that are not mainnet. The
chain
option was not being passed to the node and Etherscan clients. - Support of additional Etherscan explorers like optimistic, avalanche and fantom
- ETH balance of first called contract for value transfers
Maintenance
- Updated examples
- Updated QuickNode and Chainstack trace support
The updated value transfer usage with the new onlyToken
option.
Usage: tx2uml value <txhash(s)> [options]
Generates a UML sequence diagram of token and ether value transfers between accounts and contracts. This requires an archive node that supports debug_traceTransaction with custom EVM tracers which are Geth, Erigon or Anvil.
Arguments:
txHash(s) transaction hash or an array of hashes in hexadecimal format with a 0x prefix. If running for multiple transactions, the comma-separated list of transaction hashes must not have white spaces
Options:
-e, --onlyToken get transfers only from token events. No ETH transfers will be included. Use when provider does not
support debug_traceTransaction with custom tracer. (default: false)
-h, --help display help for command
Polygon Only Token Transfers
If there is no access to a node provider that supports debug_traceTransaction
with a custom EVM tracer, you can generate a value transfer diagram just from the token events.
Use the -e --onlyToken
option to just get the token events. This means no ETH transfers in the transaction will be included which are sourced from calling debug_traceTransaction
.
The following example is a mStable mUSD swap transaction on Polygon 0xd96e4fa0b545652e99b35aee027246cb14739e27e7d74d92eb3875380f1e71ea.
The -c, --chain
option is used so the contract ABIs are retrieved from Polygonscan and the Polygon token details contract is used.
tx2uml value 0xd96e4fa0b545652e99b35aee027246cb14739e27e7d74d92eb3875380f1e71ea --onlyToken --chain polygon -o ./polygon-musd-swap