> For the complete documentation index, see [llms.txt](https://docs.playnance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playnance.com/explorer-and-transaction-visibility/playblock-explorer-and-transaction-visibility.md). # PlayBlock Explorer & Transaction Visibility Transparency is a core requirement of any credible blockchain.\ On [PlayBlock](https://explorer.playblock.io/), every transaction, contract call, and token movement is fully observable in real time through a dedicated blockchain explorer powered by [Blockscout](https://www.blockscout.com/). This article explains how PlayBlock uses Blockscout, what data is visible, and why transaction visibility is critical for games, partners, and users. ### What Is the PlayBlock Explorer? The [PlayBlock Explorer](https://explorer.playblock.io/) is the public window into the PlayBlock network. It allows anyone (users, developers, auditors, partners) to independently verify what happens on-chain, without trusting PlayBlock servers, APIs, or dashboards. Through the explorer you can inspect: * Blocks and block production * Transactions and confirmations * Wallet balances and histories * Smart contracts and verified source code * Token transfers (GCOIN, USDP, and others) * Game-related events (bets, payouts, rewards) PlayBlock’s explorer is built on Blockscout to provide a battle-tested, open-source, and industry-standard visibility layer. ### Why Blockscout? Blockscout is one of the most widely used explorers for EVM-compatible chains, including L2s and app-specific chains. PlayBlock chose Blockscout because it provides: * **Full EVM compatibility** – identical semantics to Ethereum tooling * **Open-source transparency** – no black-box indexing * **Advanced contract introspection** – ABI decoding, event logs, read/write views * **Token & NFT indexing** – balances, transfers, holders * **Scalability for high-throughput chains** – critical for games and micro-transactions This ensures PlayBlock remains verifiable, inspectable, and interoperable with the broader Ethereum ecosystem. ### Transaction Visibility: From Wallet to Finality Every action on PlayBlock produces an on-chain transaction that can be tracked end-to-end. #### 1. Transaction Submission When a user places a bet, receives a reward, or interacts with a game: * A transaction is signed by the user or authorized executor * It is broadcast to the PlayBlock network * A transaction hash (`txHash`) is immediately generated #### 2. Explorer-Level Tracking Using the transaction hash in the PlayBlock Explorer, you can see: * Sender and receiver addresses * Gas used and gas price * Block number and timestamp * Execution status (success / revert) * Decoded method calls (for verified contracts) #### 3. Event-Level Transparency For smart contracts, Blockscout decodes emitted events, such as: * `BetPlaced` * `GameFinalized` * `RewardDistributed` * `FundsTransferred` This is especially important for gaming logic, where outcomes must be provably fair and auditable. ### Smart Contract Verification PlayBlock actively verifies its core smart contracts on Blockscout. This means: * Source code is publicly available * Bytecode matches deployed contracts * Anyone can review logic, limits, and safeguards * External auditors and partners can independently validate behavior Verified contracts also unlock: * Human-readable function calls * Decoded event logs * Read-only contract state inspection This is critical for trust in financial and gaming systems. ### Token Visibility (GCOIN, USDP, and More) The explorer provides full token-level transparency: * Token metadata (name, symbol, decimals) * Total supply and circulating supply * Holder distributions * Transfer history per wallet * Contract-level mint/burn events For PlayBlock-native tokens like GCOIN, this ensures: * Rewards are verifiable * Emissions are auditable * Treasury movements are visible * No hidden inflation or off-chain accounting ### Game & Reward Transparency Unlike traditional platforms where balances live in databases, PlayBlock games settle on-chain. This means: * Rewards sent to wallets are publicly visible * Jackpot payouts can be independently verified * Treasury and vault contracts are observable * No “invisible” balance adjustments ### Developer & Partner Benefits For developers and partners, the explorer is not just a UI — it’s a debugging and monitoring tool: * Trace failed transactions * Inspect gas usage * Verify executor behavior * Monitor contract upgrades * Audit partner revenue flows This drastically reduces trust assumptions between PlayBlock and third-party operators. ### Transparency as a Design Principle PlayBlock does not treat the explorer as an afterthought. Transaction visibility is: * A security feature * A compliance enabler * A trust mechanism * A developer productivity tool By building on Blockscout and exposing the full on-chain lifecycle, PlayBlock ensures that nothing important happens off-chain or out of sight. ### Summary * PlayBlock uses Blockscout as its official blockchain explorer * Every transaction, contract call, and reward is publicly visible * Smart contracts are verified and auditable * Token flows are transparent and traceable * Users and partners never need to “trust the backend” --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.playnance.com/explorer-and-transaction-visibility/playblock-explorer-and-transaction-visibility.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.