Indexed ArweaveBlockchain Data

Arweave has produced blocks since its 2018 launch, and its ledger is a weave rather than a chain: each block links to its predecessor and to a recall block drawn from history, so mining requires holding old data instead of only recent state. That requirement is Proof of Access. An upload is priced once, and the fee funds an endowment that keeps paying miners to store those bytes long after the transaction settled. AR is the native token, divisible into a trillion winston, with most of the supply created in the genesis block. Balances are held against addresses derived from a wallet’s own public key, and every transaction can carry arbitrary name-and-value tags, which is how applications find data they wrote years earlier. Celestia sells availability for a window; this chain sells storage with no end date.

SonarX indexes what the ledger records: blocks, transactions with their sizes, fees and tags, the bundles inside them and the data items each carries, wallet balances and mining rewards. The same normalized model is used on every chain SonarX covers, so this activity joins to other networks in one query.

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

Bundling is what makes this chain deceptive. Under ANS-104 one paid transaction can hold thousands of data items, each signed by its own owner and carrying its own tags, and a bundle can contain further bundles. Read only the top layer and many separate writes by separate authors look like a few large uploads by a few payers. SonarX unwraps the nesting and indexes the items themselves, so attribution follows the signature rather than the fee. Tags are the second seam: free-form strings each application uses as its own index.

Storage-cost accounting is the first workload: what an application or archive paid per byte, when, and how that price moved, which is readable because the fee and the size sit on the same record. Application analysis is the second and runs on tags, since the network has no contracts to group activity by and a publisher’s footprint is defined by the tag conventions it chose. Attribution work is the third, separating the service that paid for a bundle from the accounts that signed the items inside it. Reward and endowment accounting is the fourth, tracking what miners were actually paid. Token analytics covers the asset side of that across networks, and Sia is the usual comparison when the question is what storage costs.

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 you need bundled items resolved to their signers, because that is the difference between a narrow dataset and a very wide 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.