Multi-Explorer Data Reconciliation Tool

WHAT IT DOES

This tool reconciles contract data across multiple block explorers to identify discrepancies in transaction counts, logs, source code, and ABI presence. It queries data from multiple explorer APIs (Etherscan, Blockscout, Sourcify, and custom endpoints) and compares the results to detect inconsistencies. The tool analyzes transaction counts, log/event counts, source code hashes, and ABI availability, flagging any mismatches between explorers. Results are presented as a detailed reconciliation report with itemized checks, status indicators, and explorer-by-explorer comparisons. This is essential for developers verifying contract data consistency, auditors cross-checking on-chain information, and teams ensuring data reliability across different block explorer sources.

HOW TO USE

Connect your wallet (read-only, no transaction required) and select the target network. Enter the contract name and address, specify the explorers to reconcile (comma-separated, e.g., "etherscan, blockscout, sourcify"), and set the block range for data comparison. Click "reconcile data" and the tool will query each specified explorer, compare the data, and generate a reconciliation report. Results display a summary with contract details, explorers checked, overall consistency status, detailed reconciliation cards showing each check type with status and explorer comparisons, and a table of all reconciliation results. Use the report to identify data discrepancies, verify contract information across sources, and investigate potential data quality issues.

TECHNICAL MECHANISM

The reconciler uses ethers.js v5.7.2 to perform a multi-stage data reconciliation process. First, it calls eth_getCode to verify the contract is deployed and uses multiple block explorer APIs (Etherscan, Blockscout, Sourcify) to fetch source code, ABI, and contract metadata. The tool queries eth_getLogs and eth_getTransaction across the specified block range from each explorer's associated RPC endpoint to retrieve transaction and log data. It then compares the data across explorers for each metric: transaction count, log/event count, source code hash (using SHA-256 of the source code), and ABI presence. For each metric, the tool determines a consensus value (e.g., the median or most common value) and flags any explorer that deviates from the consensus beyond a configurable tolerance. Discrepancies are highlighted with detailed explorer-by-explorer comparisons. Results are compiled into a structured report with itemized checks, status indicators (ok/warn/bad), and explorer-specific values for each metric.

WHAT IT CANNOT SEE

This tool cannot reconcile data from explorers that are not accessible via API or that require authentication. It is limited by the RPC provider's rate limits and block range availability for historical data; very old blocks may be inaccessible on some endpoints. It cannot reconcile data from private or permissioned chains that are not accessible via the provided RPC endpoints. The analysis relies on the accuracy and completeness of data from multiple sources; if one explorer has incomplete data, it may produce false discrepancies. It cannot resolve discrepancies without manual review or additional data sources—the tool identifies discrepancies but does not determine which source is correct. The tool is limited to the specific block ranges and contract instances that are accessible via RPC. It cannot guarantee that reconciliation captures all possible discrepancies without comprehensive cross-referencing across all available data fields. Reconciliation results are based on the data available at the time of the query; data may change if explorers update their indices or if new blocks are added.

PLEASE NOTE

This is a read‑only analytics tool—it never submits transactions or modifies contract state. It is designed for EVM‑compatible chains and works with major block explorer APIs. The reconciliation results are for informational and audit purposes only and should be manually verified when discrepancies are found. Different explorers may have different indexing latencies or data retention policies, which can affect reconciliation results. Consider the block range and explorer-specific characteristics when interpreting the results.