Indexed DashBlockchain Data

Dash has produced blocks since 18 January 2014, first as Xcoin, then Darkcoin, and under its current name since March 2015. Mining uses X11, a chained sequence of eleven hash functions, blocks target 2.6 minutes, and difficulty is retargeted on every block by Dark Gravity Wave. The ledger is UTXO, inherited from Bitcoin, so there are no accounts and a holder owns outputs rather than a balance. DASH is capped below nineteen million, and the subsidy steps down by roughly a fourteenth every 210,240 blocks, about once a year, instead of halving. What separates the chain from the rest of the family is its second tier. Masternodes lock 1,000 DASH as collateral and are registered on chain, quorums drawn from that registry threshold-sign ChainLocks that settle the tip within a block or two, and a tenth of every block reward funds a treasury that the same operators allocate by vote. Mixing is a wallet feature built on CoinJoin, not a protocol-level privacy layer.

SonarX indexes blocks and headers, transactions, inputs and outputs, the locking scripts, the special transaction types that carry masternode and quorum state, coinbase payouts, and the address-level positions derived from the output set. Those records use the same normalized model as every other network SonarX indexes, so Dash can be queried beside the rest of the UTXO family without a second dialect.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Kafka streaming can be enabled for Dash on request.

Half of what matters here is not a payment. Special transactions register, update and revoke masternodes and commit quorums, and the deterministic list they produce is state that has to be replayed in order, because an operator’s place in the payment queue depends on when it entered and whether it was ever revoked. Coinbase output is split between the miner, the operator due next and the treasury, so subsidy attribution needs the list as it stood at that height rather than a single output. Mixing adds a third job: CoinJoin rounds look like ordinary transfers with repeated denominations, and the indexed data records the pattern without inferring who paid whom.

Payment monitoring is the common workload: a processor settling in DASH needs every deposit and withdrawal reconciled against internal records, across change outputs a UTXO wallet generates on each spend. Operator economics is the distinctive one, and it exists on very few chains. Restating what a masternode actually earned means joining its registration and collateral history to the subsidy outputs it received, at the height each one paid. Treasury accounting is a third, following proposal payouts as ordinary outputs and comparing what was voted for against what was spent. Compliance teams take a fourth view, flagging CoinJoin participation as an attribute of a transaction rather than a conclusion about it. Wallet analytics covers the address-level side of this across chains, and Zcash is the usual comparison when the question is about confidentiality.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Dash history is available now, and streaming is provisioned on request. It is worth saying whether the masternode and quorum records are in scope, since they are the part of this chain that has no equivalent elsewhere. 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.