The EVM Networks Project Documentation
  • Project Presentation
  • Overview
    • Mission & Vision
    • Features
  • Project Initialization
    • Prerequisites
    • Installation
  • Project Usage
    • Networks
    • Providers
    • Endpoints
  • Data Models
    • Network Model
    • Native Currency Model
    • RPC Node Model
    • RPC Provider Model
    • Block Explorer Model
    • Contract Model
    • Interface Definition
  • Data Accounted Entries
    • Networks
    • Providers
    • Contracts
  • EVM Tools
    • Tools
  • Resources
    • EIPs
    • Contracts
    • References
Powered by GitBook
On this page
  1. Data Models

Block Explorer Model

EVM Network Block Explorer Data Model Documentation

PreviousRPC Provider ModelNextContract Model

Last updated 2 years ago

CtrlK
  • Name
  • Block Explorer
  • Type
  • Standard
  • Browser URL
  • API URL
  • Docs URL

Name

description: alphanumerical official human readable name

type: string - required

requirements

  • format: more than 0 characters & less than 41

  • standard: official name to identify block explorer & unique [in network block explorers data set]

Block Explorer

description: alphanumerical ID that uniquely identifies block explorer

type: string - required

requirements

  • format: more than 0 characters & less than 21

  • standard: short name that identifies block explorer & unique [in network block explorers data set] & exact to the object instance key

Type

description: specification type of block explorer

type: string - required

requirements

  • format: blockscout | etherscan | independent | subscan | null

  • standard: must tag block explorer depending on the API endpoints schema

Standard

description: EIP standard specification of block explorer

type: string - required

requirements

  • format: eip3091 | none | null

  • standard: must tag block explorer depending on the browser endpoints schema

Browser URL

description: RPC provider main information link

type: string - required

requirements

  • format: start with "https://" & have more than 9 characters

  • standard: must use HTTPS protocol

API URL

description: RPC provider API endpoint base URL

type: string - required

requirements

  • format: start with "https://" & have more than 9 characters

  • standard: must use HTTPS protocol

Docs URL

description: RPC provider main API documentation link

type: string - required

requirements

  • format: start with "https://" & have more than 9 characters

  • standard: must use HTTPS protocol