Indexed Avalanche PBlockchain Data

The P-Chain is the platform chain of Avalanche, one of the three chains that have made up the primary network since its 2020 launch, and it is where the network keeps track of itself. It runs the Platform VM under the same Snowman consensus as its siblings, and it has no EVM: no contracts, no receipts, no event logs. Its transactions are typed instead. Validators and delegators are registered with a stake and a fixed term, subnets and the blockchains inside them are created, and AVAX is imported from or exported to the other two chains. The bookkeeping is a UTXO model, so a stake is an output locked until its term ends rather than a balance marked as bonded, and addresses are bech32 strings carrying a P- prefix rather than the twenty-byte hex the C-Chain uses. Staking the primary network takes at least 2,000 AVAX.

SonarX indexes the records this chain keeps: blocks, its typed transactions, validator and delegator registrations with their terms and commission shares, subnet and blockchain creation, reward outputs, the UTXO set behind them, and the imports and exports that move AVAX between chains. The same normalized model is used on every chain SonarX covers, so staking records line up with execution activity elsewhere.

Full historical coverage is provisioned for Avalanche P-Chain on request.

Staking here is a term, not a stream. Nothing credits a validator per block: the record is a registration, a duration and a single reward output when the term closes, so a reward series has to be reconstructed from those three facts, with the commission share applied before a delegator’s cut is known. Identity is the second problem. The same operator holds bech32 addresses here and hex addresses on the C-Chain, and no transaction ties the two, so attribution runs through the export and import pair that moved the AVAX. Those pairs are also why a balance history built here alone shows value arriving from nowhere.

Reward accounting is the workload this dataset exists for: what a validator earned across terms, what its delegators were owed after commission, and what a customer’s position actually returned. Staking analytics is the solution area that work sits in across the networks SonarX indexes. Stake-distribution research is the second, measuring concentration and turnover in the validator set over time. Network registry tracking is the third, following which subnets and blockchains were created and who secures them. Supply work is the fourth, since a complete AVAX position spans three chains and only reconciles when the transfers between them are matched. Ethereum Beacon Chain presents the same separation for a different network.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Say whether C-Chain records are in scope as well, because most questions that start here end up crossing over. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.