Indexed Neo LegacyBlockchain Data

Neo Legacy is the ledger Neo ran before N3: the chain that started in 2016 under the name AntShares and took the Neo name the following year. Consensus is dBFT, which reaches agreement within a block, so blocks here are final when written. Its accounting is the part worth knowing. NEO and GAS were global assets tracked as unspent transaction outputs, so a native balance was the sum of outputs an address could spend rather than a stored number, while NEP-5 tokens kept their balances inside contract storage and reported movement through notifications. Contracts ran on the older NeoVM, addresses were base58 strings beginning with the letter A, and NEO was indivisible then as now. When Neo N3 launched in 2021 the project’s own guidance was that this network moved into long-term support, with a migration contract swapping tokens one for one into the new chain.

SonarX indexes the ledger as it was recorded: blocks, transactions with their inputs and outputs, the unspent-output set behind NEO and GAS, contract invocations and their notifications, NEP-5 transfers and balances, claim transactions for generated GAS, and derived address balances for both asset kinds. Everything is normalized into the model SonarX uses across every network it covers, so this chain reads next to N3 rather than through a bespoke parser.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

One chain, two models, and a transfer view has to union them. Native-asset movement is spends: an input names an earlier output, so a NEO or GAS balance is reconstructed by replaying the output set the way a UTXO chain demands. NEP-5 movement is contract state, visible only through the notifications a contract chose to emit, so the two halves of a wallet’s history sit in different places and carry different guarantees. Identity separates the datasets cleanly, because an address here begins with A and its N3 counterpart begins with N, so the only real link between the two ledgers runs through migration transactions.

Historical position reconstruction is the first workload: custodians and funds that held NEO or a NEP-5 token before the migration need those balances restated at dates that predate N3 entirely. Migration analysis is the second and it is specific to this pair, following which holdings crossed to the new chain, when, and how much never moved at all. Long-run token research is the third, since a number of early token projects issued here and nowhere else. Token analytics covers that work across chains, and Neo N3 holds everything after the migration.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. The Legacy history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether N3 is in scope too, because matching a holder across both ledgers is a different job. 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.