Skip to main content

Blockscout — Usage Guide

Blockscout is the official explorer of the ISBE network. It allows consulting blocks, transactions, accounts, and contracts deployed in the different environments (dev, pre, and pro). This tool is useful for both developers and functional teams who need to verify the on-chain activity of their use case.

1. Access to the Explorer​

The ISBE network has one Blockscout explorer per environment. Each use case will receive the corresponding links when their environment is activated.

URL structure:

  • ISBE-DEV: https://blockscout.dev.isbe.network (not real)
  • ISBE-PRE:
    • Case Network: https://blockscout-main.pre.portal.redisbe.com
    • Bare Network: https://blockscout-bare.pre.portal.redisbe.com
  • ISBE-PRO:
    • Case Network: https://blockscout-main.portal.redisbe.com
    • Bare Network: https://blockscout-bare.portal.redisbe.com

2. Main Functions​

Blockscout allows:

2.1. Consulting Blocks​

  • Block height
  • Validators who have signed the block
  • Number of included transactions
  • Timestamp
  • Block hash

2.2. Consulting Transactions​

Includes:

  • Transaction status (success / failed)
  • Gas used
  • Input data (useful for decoding functions)
  • Events emitted by the contract
  • Issuer signature and address

2.3. Consulting Deployed Contracts​

Allows:

  • Viewing contract address
  • Verified source code (if uploaded)
  • Public ABI (if desired to be shared)
  • Visible events and functions
  • Direct interaction from the interface (if enabled)

2.4. Consulting Accounts and Balances​

Includes:

  • Simulated ETH balance (no economic value)
  • Transaction history
  • Interactions with contracts

3. Contract Verification​

Use cases can verify their contract on the explorer, which allows:

  • Showing the source code
  • Exposing the ABI
  • Facilitating audits and external validation
  • Enabling direct interaction from Blockscout

The process depends on the environment configuration, but typically consists of:

  1. Compiling the contract with deterministic parameters.
  2. Uploading source code and metadata to the explorer.
  3. Confirming the address and constructor arguments.

Consult the ISBE team if verification is enabled in your environment.

4. Known Limitations​

  • Blockscout may take several seconds to index a newly generated block.
  • Some advanced interaction functions may be disabled depending on the environment.
  • Automatic contract verification is not always available in dev.
  • In permissioned networks, certain public statistics may be simplified.

5. Usage Best Practices​

  • Always verify the transaction in Blockscout after a critical deployment.
  • For advanced debugging, combine Blockscout with RPC logs from the regular node.
  • Review contract events to validate expected behavior.
  • If a transaction appears as pending for too long, contact ISBE.

6. Summary​

Blockscout is an essential tool for:

  • Validating that transactions are executed correctly.
  • Inspecting contracts, events, and calls.
  • Performing basic audit of blockchain activity.

It should be used alongside assigned RPC nodes and use case monitoring to obtain a full view of on-chain behavior.