Wallet and contract addresses
Source addresses, destination addresses, deposit accounts, token contracts, spender contracts, and program accounts can appear in public transaction data depending on the network.
A field-by-field explanation of the addresses, amounts, assets, timing, fees, approvals, contracts, and route records that may remain visible.
Source addresses, destination addresses, deposit accounts, token contracts, spender contracts, and program accounts can appear in public transaction data depending on the network.
Native-asset values, token transfer amounts, balances, approvals, minimum outputs, and contract event data can be public. Display precision and decoded labels depend on the explorer or analytics service.
Block time, transaction order, confirmation height, source and destination timing, and later wallet activity can provide context. Timing alone does not always prove common control.
Gas used, gas price, priority fees, programs or contracts called, approval actions, and execution success or failure can remain visible.
A source deposit and destination delivery can exist on different chains with different hashes and explorers. Route providers may also retain operational records outside public blockchains.
Privacy-focused routing does not erase these public records. Where offered, it is intended to reduce an obvious direct source-wallet to receiving-wallet association within the supported route structure.
A blockchain address does not inherently contain a legal name, but public or private contextual data may associate an address with a person or organization.
Yes. Depending on the network, a failed transaction and its fee or execution details can remain in public history.
No. Public source and destination records can remain.