A common portfolio layer is useful only when it preserves the account, transaction, asset, and finality rules of each underlying network.
Every chain chart needs scope, assets, valuation, flows, and data quality. The evidence underneath differs. Ethereum uses accounts and contract events. Solana distributes state across accounts and programs. Bitcoin balances emerge from UTXOs and descriptors. Multi-chain views need canonical identifiers and bridge reconciliation.
Start with the chain-specific guide, then use the Web3 and data-model pages to understand how a consolidated portfolio can aggregate values without erasing native meaning. Each guide links to a longer article with implementation and interpretation details.
Each layer answers a different question. The summary remains useful because the supporting evidence is still available.
Accounts, contract tokens, gas, event logs, approvals, staking, and DeFi positions.
Token accounts, mints, programs, instructions, SOL states, and dense activity streams.
UTXOs, descriptors, change, confirmations, fee rates, and privacy-aware scope.
Canonical identifiers, bridge transfers, wrapped assets, app state, and permissions.
Definitions are descriptive, not promises of completeness. Protocol and network implementations can differ.
A network model in which state is associated with accounts and updated by transactions.
A model in which spendable value is represented by unspent transaction outputs.
Data controlled or modified by onchain programs, potentially spread across many accounts.
The network-specific confidence that a transaction will not be reversed.
The chain’s built-in asset used for value transfer and often transaction fees.
An asset or claim created on one chain based on value locked or burned elsewhere.
A shared event envelope can help, but chain-specific adapters are required to preserve native transactions, accounts, state, and finality.
They may use different scope, token lists, pricing, confirmation rules, protocol resolvers, or spam filters.
Included networks and accounts, valuation cutoff, pricing sources, unsupported positions, bridge reconciliation, and stale data.
Long-form articles expand the data model, chart choices, and limitations for this topic.
A practical framework for charting Ethereum accounts, ERC-20 balances, contract interactions, gas, staking, lending, and other onchain positions.
Understand Solana wallet charts through the network’s account model, token accounts, programs, instructions, fees, compressed assets, and high-frequency activity.
Learn why Bitcoin wallet charts must be built from unspent transaction outputs, address scope, change detection, fees, and careful privacy assumptions.
Use clear scope, explicit valuation, reconciled flows, position-aware exposure, and visible data quality in every wallet chart.