Knowledge Base

MetaCoin is a permissioned, Hyperledger-Fabric–based blockchain network operated by Inblock. It supports both fungible tokens (the MRC-010 standard) and non-fungible tokens (the MRC-401 and MRC-402 standards). The native asset, MTC, is used for paying network fees, settling token swaps, and participating in token sales. The network finalizes blocks every few seconds, so transactions appear on Bluescan almost immediately after they are submitted.

Bluescan is the official block explorer for the MetaCoin blockchain. It indexes every block, transaction, token registration, NFT mint, and lock event into a queryable database, then exposes that data as web pages and a public REST API. Bluescan is operated by the same team that maintains the MetaCoin network and is free for public use. There is no account required to read on-chain data.

A wallet stores your private keys and lets you sign and submit transactions. An explorer like Bluescan is read-only — it cannot move funds or sign anything. You use a wallet to act on the network and Bluescan to verify what happened. Many people use both side by side: send a transaction with the wallet, then paste the transaction hash into Bluescan to confirm it was included in a block.

Paste the value into the search bar at the top of any page. Bluescan auto-detects five formats: a numeric block height, a 64-character block or transaction hash, a 40-character wallet address starting with "MT", a numeric or alphanumeric token ID, or an MRC-402 NFT identifier. If your input matches more than one thing the explorer routes you to the most specific match (transaction beats block beats address).

Three common causes. (1) The hash belongs to a different chain or test network. Make sure you are looking at the mainnet explorer at bluescan.io. (2) The hash was truncated when copying — verify it is exactly 64 hexadecimal characters. (3) The transaction is still pending and has not yet been included in a block; wait a few seconds and reload. If none of those apply, the transaction may have been rejected; check your wallet's outgoing tx log for an error message.

MRC-010 is the fungible token standard on MetaCoin, conceptually equivalent to ERC-20 on Ethereum. Each MRC-010 token has a numeric ID, a name, a symbol, a decimal precision (commonly 8), an owner address, and an immutable initial supply. After registration the supply can grow only via explicit Increase events or shrink via Burn events, both of which appear in the token's History tab.

A locked balance is a portion of the holder's tokens that is bound by an unlock timestamp. Locks are commonly created by token sales, vesting agreements, or treasury policies. Bluescan computes the lock state in real time from the wallet's on-chain balance entries: any chunk whose unlockdate is in the future is shown as locked, with a countdown to the earliest unlock. After the timestamp passes the lock label disappears automatically on the next page load.

When a token is registered the issuer can pre-allocate portions of the supply to specific addresses; each allocation is recorded as a Reserve event in the same block as the Token Create event. Reserves are not transfers — the wallets simply appear pre-funded as soon as the token exists. The Reserve tab on a token page lists every initial allocation along with its destination address.

MRC-401 is single-issue: each NFT exists in exactly one copy and has one current owner. It is appropriate for unique digital art, certificates, or one-of-a-kind collectibles. MRC-402 is multi-edition: a single registration can mint many fungible-but-themed copies that holders can later "melt" (burn for value) or trade individually. Bluescan renders both standards on similar-looking pages, distinguished by a colored protocol badge in the corner.

NFT image data is supplied by the creator at registration time and may be either an HTTPS URL or an embedded base64 payload. If the URL has gone offline, or if the image data is in a format Bluescan does not consider safe to render (for example inline SVG, which can carry script payloads), the explorer falls back to the Bluescan logo so the rest of the page remains usable. The on-chain data itself is unaffected.

Bluescan does not require an account, does not ask for your wallet, and does not collect personally identifiable information. The site uses standard server access logs (IP, user agent, request path, and response time) for operational monitoring and security; these logs are retained for a limited period and are not shared with third parties. We embed Google AdSense, which may set its own cookies — see the Privacy page for details.

Looking up an address on Bluescan reveals only what is already public on the blockchain. The MetaCoin ledger is transparent by design, so anyone with the address can already see the balances and transaction history regardless of which explorer they use. Bluescan stores no private keys and cannot move any funds.

Yes. The free, unauthenticated API mirrors most read endpoints used by the web UI and is appropriate for low-volume integrations such as personal dashboards or Telegram bots. For higher rate limits, custom themes, or production traffic please refer to the API Plans page. The endpoint reference is available at /api-docs.

429 means you exceeded the per-minute quota assigned to your IP or API key. The response includes a Retry-After header indicating how long to wait. To avoid throttling, batch your requests, cache aggressively on your side, or upgrade to a paid plan with a higher quota.

Yes. The web explorer is completely free and does not require any registration. The free API tier is also free and has rate limits intended for hobby or development use. Paid API tiers, white-labeled "Explorer-as-a-Service" deployments, and priority support are commercial products — see the corresponding pages.

Confirmed security issues should go to the Bug Bounty page where the disclosure process and rewards are described. Non-security feedback (UX issues, missing data, suggestions) is welcome via the Contact page or the email address listed there. We read every message; please include the URL where you saw the problem and a brief description.

Yes — direct linking to any Bluescan page is encouraged and the URLs are stable. For embedding rendered widgets we recommend the API plus your own UI; iframe embedding of full Bluescan pages is allowed but the X-Frame-Options header blocks framing for security reasons. If you need an iframe-embeddable variant, contact us about Explorer-as-a-Service.