Skip to main content

Visualization patterns

Pattern 1: Simple transfer

For basic value transfers, focus on the key elements:

Pattern 2: Transaction with instructions

For transactions with multiple instructions (based on actual Solana fixture):

Pattern 3: Smart contract interaction

For complex operations, use progressive disclosure with real field structure:

Design guidelines

1. Information hierarchy

Structure information by importance:

2. Use semantic field types

Choose the right field type for the data:

3. Color and visual cues

Use visual indicators for important information:

Chain-specific visualizations

Ethereum: Gas optimization

Show gas costs clearly:

Solana: Multiple instructions

Group related instructions (based on actual test data):

Sui: Move calls

Show Move module interactions (based on presets):

Risk indicators

High-value warnings

Unknown contracts

Irreversible actions

Testing visualizations

Before deploying a visualization, verify:
  1. Clarity: Can a non-technical user understand what will happen?
  2. Completeness: Are all important parameters shown?
  3. Accuracy: Do amounts and addresses match the raw transaction?
  4. Risk Communication: Are warnings prominently displayed?
  5. Mobile Compatibility: Does it work on small screens?
Test with different user personas (novice, regular user, expert) and edge cases like zero amounts, failed transactions, contract creation, multi-signature operations, and batch transactions.

Best practices

  1. Keep titles action-oriented: “Send ETH” not “Ethereum Transaction”
  2. Use familiar terms: “Send” not “Transfer”, “Swap” not “Exchange”
  3. Show both technical and friendly names: “Uniswap V3 (0x68b3…)”
  4. Group related information: Use list_layout for coherent sections
  5. Provide context: Include network, protocol, estimated time
  6. Be consistent: Use the same patterns across similar operations