Indexed NeoBlockchain Data

Neo, in the form covered here, is Neo N3, whose mainnet started in 2021 and replaced the protocol the project had run since 2016. Consensus is dBFT, delegated Byzantine fault tolerance, which reaches agreement inside a single block, so a written block is final and there is no confirmation depth to respect. Two native assets sit in the protocol rather than in contracts: NEO, capped at 100 million units and indivisible, which votes and elects the committee, and GAS, with eight decimals, which pays fees and is generated for NEO holders as blocks are produced. Contracts run on the NeoVM, and core functions such as the two assets, policy and contract management are native contracts inside the protocol itself. Tokens follow NEP-17, addresses begin with the letter N, and the older ledger, Neo Legacy, keeps its own history and its own address format.

SonarX indexes what N3 records: blocks and their committee, transactions and their system and network fees, contract invocations and the notifications they emit, native contract activity, NEP-17 transfers, committee votes and candidate registrations, GAS generation and claims, and derived balances for both native assets. Everything is normalized into the model SonarX uses across every network it covers, so this ledger aggregates alongside chains that look nothing like it.

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

Two properties change the bookkeeping. NEO is indivisible, so a balance is a whole-unit count and any pipeline that stores it as a decimal quantity is wrong in a way that only shows up in aggregates. GAS is generated for NEO holders block by block and then claimed later, so income exists before any transfer records it, and a holder’s earnings have to be derived from generation and claim records rather than read from movements. Activity also arrives as contract notifications rather than as logs decoded against an ABI, and the most important come from native contracts inside the protocol.

Holder and governance analysis is the first workload, and the dual-token model makes it unusually direct: NEO positions are whole units and votes are on chain, so ownership and participation are countable rather than inferred. Reward accounting is the second, reconstructing GAS generated and claimed per holder per period, which is the closest thing this chain has to a yield series. Token issuance reporting is the third, tracking NEP-17 assets from deployment onward. Token analytics covers that work across chains, and teams needing anything from before 2021 pair this share with Neo Legacy.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. N3 history is available now as a share or a file delivery, and streaming is provisioned on request. Say whether the older ledger is in scope, because that is a second share rather than a longer one. 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.