Overview
Transaction hints allow you to correlate traces with blockchain transactions. When you add a transaction hash to a trace, Mirador follows the transaction wherever it goes — across bridges, through different protocols, and onto other chains — providing full end-to-end visibility from your application code to on-chain settlement.Adding Transaction Hints
Transaction hint methods require the
Web3Plugin. See Plugins for setup.With Details
Add optional context about the transaction:With Input Data
Capture the transaction’s calldata for deeper analysis:When
input is provided, it is emitted as a "Tx input data" event via web3.evm.addTxInputData() — it is not stored in the hint. You can also call trace.web3.evm.addTxInputData(calldata) directly for the same effect.From a Transaction Object
Useweb3.evm.addTx() to automatically extract the hash, input data, and chain from a transaction-like object:
Supported Chains
| Chain | Value | Chain ID |
|---|---|---|
| Ethereum | 'ethereum' | 1 |
| Optimism | 'optimism' | 10 |
| BSC | 'bsc' | 56 |
| Polygon | 'polygon' | 137 |
| Base | 'base' | 8453 |
| Arbitrum | 'arbitrum' | 42161 |
| HyperEVM | 'hyperevm' | 999 |
Tracking a transaction on Solana or Canton? Both live outside the
Chain enum (no numeric chain ID). Use
web3.solana.addTxHint(signature) or
web3.canton.addTxHint(updateId) instead —
no chain argument required.Multiple Transaction Hints
A single trace can include multiple transaction hints. This is useful for complex operations that span multiple transactions. Mirador automatically follows each transaction across chains, bridges, and protocols, so you get full visibility into the entire flow:For Safe multisig message and transaction hints, see Safe Multisig Integration.
Complete Example
Using sendTransaction
For a more integrated approach, use sendTransaction() which automatically captures tx hints and errors:
Method Signatures
web3.evm.addTxHint
| Parameter | Type | Required | Description |
|---|---|---|---|
txHash | string | Yes | The transaction hash |
chain | ChainName | Yes | The blockchain network |
options | string | TxHintOptions | No | Description string or structured options |
web3.evm.addTx
| Parameter | Type | Required | Description |
|---|---|---|---|
tx | TransactionLike | Yes | Transaction object (hash, data/input, chainId) |
chain | ChainName | No | Override chain (auto-detected if omitted) |
web3.evm.addTxInputData
| Parameter | Type | Required | Description |
|---|---|---|---|
inputData | string | Yes | Hex-encoded transaction input data (calldata) |
web3.evm.sendTransaction
| Parameter | Type | Required | Description |
|---|---|---|---|
tx | TransactionRequest | Yes | Transaction parameters |
Best Practices
Add Hints as Soon as You Have the Hash
Don’t wait for confirmation to add the hint:Include Descriptive Details
When dealing with multiple transactions, details help identify each one:Match Chain to Transaction
Always use the correct chain for the transaction:Next Steps
Solana Transactions
Correlate Solana transactions via signature
EIP-1193 Provider
Auto-capture transactions with MiradorProvider
Traces
Learn about trace lifecycle and flushing
Transaction Tracking Example
See a complete implementation