Indexed Bitcoin CashBlockchain Data

Bitcoin Cash separated from Bitcoin after block 478,558 on 1 August 2017, in a split over how much transaction data a block should be allowed to hold. Its own first block is 478,559, and the limit has since risen to thirty-two megabytes. Everything below that stayed familiar: SHA-256 proof of work, a ten-minute block target, a UTXO ledger with no accounts, and BCH capped at 21 million with the subsidy halving every 210,000 blocks. Two protocol choices set the data apart. The difficulty algorithm was replaced in November 2020 by ASERT, which retargets on every block instead of on a 2,016-block cycle. And the May 2023 upgrade added CashTokens, so fungible and non-fungible tokens are carried inside outputs rather than by contracts. Bitcoin Cash never adopted SegWit or Taproot, so signatures stay in the input script and there is no witness section to parse.

SonarX indexes blocks and headers, transactions, inputs and outputs, the locking scripts, the derived output set, token categories attached to outputs, and address-level positions computed from all of it. The same normalized model covers every network SonarX indexes, so Bitcoin Cash sits beside the other UTXO chains and a question spanning several of them is one query.

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 Bitcoin Cash on request.

The shared prefix has to be handled first. Every output created before August 2017 exists on both networks and can be spent separately on each, so a position computed without pinning the chain counts the same coin twice. Identity is the second problem: a legacy base58 string is valid on Bitcoin too, and CashAddr re-encodes the same hash, so matching happens on the hash rather than on the text a wallet displays. CashTokens then push token bookkeeping into the output walk, because a category and its amount are output properties and supply is only correct once every spend has been applied.

Payment work dominates. Processors and merchants settling in BCH need every deposit and refund in one place, matched against internal ledgers rather than sampled, which is a join from spends back to the outputs they consume. Custody reconciliation is the second, and here the fork is the whole difficulty: a restated holding has to keep the pre-split coins attributed to the right network and resolve both address encodings to one owner. Token issuance analysis is newer, following a CashToken category from its genesis output to the addresses still holding it. Wallet analytics covers the address-level side of this across chains, and Litecoin is often pulled alongside when the question is about payment settlement rather than about one asset.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Bitcoin Cash history is available now, and streaming is provisioned on request. Say whether the pre-split blocks should be included, because that decision changes what a balance means. 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.