Verify in my browser
Your browser downloads the DCRC-20 transactions, replays them with the same rules as the indexer and compares the resulting state.
Look up a transaction
In ranges of 500 blocks, in a Web Worker: the page stays usable.
What this verification proves, and what it does not
The rules (curve, pool, ICO, route, fees) are public code, identical in the indexer and in your browser. Two validators replaying the same blocks reach the same state.
Here, the server supplies the transactions. If the indexer computed a balance wrongly, the divergence would be detected.
However, if the server omitted a transaction, your browser could not see it: that requires an independent block source (Blockbook, planned).
The transactions themselves are in Dogecoin blocks: their order is decided by miners, and their signature validity by Dogecoin consensus.
Sources
- DCRC-20 transactions per block: https://api.stonkdoge.money/v1/verify/blocks
- Rules: the @dcrc/core package (the same code as the indexer).
- Independent block source (Blockbook): planned.