Data verification
MyBitcoinExplorer operates Bitcoin Core on mainnet with pruning disabled. Blocks are downloaded from Bitcoin peers and validated locally. The explorer does not call an external Bitcoin data API to populate missing chain facts.
Synchronization and indexes
Blockchain validation and address indexing are separate processes. The live status page reports the verified block height and index readiness. Results include observation context; unavailable or incomplete data is not presented as a zero balance or a current network observation.
Transactions and graph edges
A transaction input references an earlier output. That spending relationship is a factual graph edge. It does not establish the identity of the owner, whether two addresses share ownership, or which output corresponds to one particular input.
Labels and research
Future entity labels will need evidence, provenance and review. Change detection, common-input clustering and fund-allocation methods are heuristics that can fail, especially for collaborative transactions. They will never be silently presented as proven identity.
Time and fee estimates
A block header’s timestamp is not an exact transaction creation time. Fee estimates reflect the node’s observations and do not guarantee inclusion. If observations are insufficient, we show unavailable.
Privacy and monitoring
Public chain data does not make your private watchlists, labels, searches or investigations public. Account-owned data will be access controlled. Payment invoices will be associated with accounts internally, without publishing that association.