Blockchain explorer

The block explorer is your gateway to the world of Hash Ahead data. You can view real-time blocks, transactions, miners, accounts and other related activities on the chain through the block explorer.

Data

Hash Ahead is transparent by design, and all information can be verified. Block explorers provide an interface for obtaining this information. This applies to Hash Ahead's mainnet and testnet, if you need the data. Data is divided into execution data and consensus data. Execution data refers to transactions that have been executed within a specific block. Consensus data refers to the blocks themselves and the validators who proposed them.

Below is a summary of the types of data you can get from a block explorer.

Execution Data

New blocks are added to Hash Ahead every 20 seconds (unless the block proposer misses the opportunity to propose), so there is a near-steady stream of data being added to the block explorer. Blocks contain a lot of important data that you may find useful:

Standard Data

  • Block height – the block number and length of the blockchain (in blocks) when the current block was created

  • Timestamp - the time the block was proposed

  • Transactions – the number of transactions included in the block

  • Transaction Fee Recipient - The address to get the gas fee tip from the transaction

  • Block reward - the amount of HAH awarded to the validator who proposed the block

  • Size - the size of the data in the chunk in bytes

  • Gas consumed – the total number of gas units consumed by the transactions in the block

  • Gas limit – the total gas limit set by the transactions in the block

  • Gas base fee - the minimum multiple required for a transaction to be included in a block

  • Burned Fee - Amount of HAH burned in the block Other data - any additional data added to the block by the miner

Advanced Data

  • Hash - Represents the cryptographic hash of the block header (the block's unique identifier)

  • Parent hash - the hash of the previous block of the current block

  • State Root – The root hash of the Merkle prefix tree that stores the state of the entire system.

Froce

A block explorer will not only give you data on transactions and gas usage in blocks, but also give you information on the network's current gas price. This will help you understand network usage, submit secure transactions and avoid gas overspending. Look for APIs that can help you get this information into your own product interface. Fuel-specific data covers:

  • Estimated number of fuel units (along with estimated price and duration) required for a safe but slow transaction

  • Estimated number of fuel units required for general transactions (along with estimated price and duration)

  • Estimated number of fuel units required for a quick transaction (along with estimated price and duration)

  • Average confirmation time based on gas price

  • Contracts that are burning gas - in other words, popular products that are being heavily used on the network

  • Accounts that are consuming gas – in other words, heavy web users

Trade

Block explorers have become a common place for people to track the progress of transactions because of the extra certainty provided by the level of detail you can get. Transaction data includes:

Standard data

  • Transaction hash - A hash generated when the transaction is submitted

  • Status - An indication of whether the transaction is pending, failed or a success

  • Block - The block in which the transaction has been included

  • Timestamp - The time at which a miner mined the transaction

  • From - The address of the account that submitted the transaction

  • To - The address of the recipient or smart contract that the transaction interacts with

  • Tokens transferred - A list of tokens that were transferred as part of the transaction

  • Value - The total HAH value being transferred

  • Transaction fee - The amount paid to the miner to process the transaction (calculated by gas price*gas used)

Advanced data

  • Gas limit - The maximum numbers of gas units this transaction can consume

  • Gas used - The actual amount of gas units the transaction consumed

  • Gas price - The price set per gas unit

  • Nonce - The transaction number for the from address (bear in mind this starts at 0 so a nonce of 100 would actually be the 101st transaction submitted by this account

  • Input data - Any extra information required by the transaction

\

Accounts

There's a lot of data that you can access about an account. This is why it's often recommended to use multiple accounts so that your assets and value can't be easily tracked. There are also some solutions being developed to make transactions and account activity more private. But here's the data that's available for accounts:

User accounts

  • Account address - the public address you can use to send funds to

  • HAH Balance - Amount of HAH associated with this account

  • Total HAH Value - Value of HAH

  • Token - the token associated with the account and its value

  • Transaction History - a list of all transactions for which this account was a sender or receiver

Smart contracts

Smart contract accounts have all the data that a user account will have, but some block explorers will even display some code information too. Examples include:

  • Contract creator - The address that deployed the contract to Mainnet

  • Creation transaction - The transaction that included the deployment to Mainnet

  • Source code - The solidity or vyper code of the smart contract

  • Contract ABI - The Application Binary Interface of the contract—the calls the contract makes and the data received

  • Contract creation code - The compiled bytecode of the smart contract—created when you compile a smart contract written in Solidity or Vyper, etc.

  • Contract events - A history of the methods called in the smart contract—basically a way to see how the contract is being used and how often

Tokens

Tokens are a type of contract so they'll have similar data to a smart contract. But because they have value and can be traded they have additional data points:

  • Type - Whether they're an HRC-20, HRC-721 or another token standard

  • Price - If they're an HRC-20 they'll have a current market value

  • Market cap - If they're an HRC-20 they'll have a market cap (calculated by price*total supply)

  • Total supply - The number of tokens in circulation

  • Holders - The number of addresses that hold the token

  • Transfers - The number of times the token has been transferred between accounts

  • Transaction history - A history of all the transactions including the token

  • Contract address - The address of the token that was deployed to Mainnet

  • Decimals - HRC-20 tokens are divisible and have decimal places

Network

Some block data focuses more fully on the health of Hash Ahead.

  • Total Transactions - Number of transactions since Hash Ahead was created

  • Transactions per second - the number of transactions that can be processed per second

  • HAH Price - The current market price of 1 HAH

  • Total HAH Supply - the amount of HAH in circulation — remember that new HAH is created with each block as a block reward

  • Market cap - the calculation result of price * supply

CONSENSUS LAYER DATA

Epoch

For security reasons, randomized committees of validators are created at the end of every epoch (every 6.4 minutes). Epoch data includes:

  • Epoch number

  • Finalized status - Whether the epoch has been finalized (Yes/No)

  • Time - The time the epoch ended

  • Attestations - The number of attestations in the epoch (votes for blocks within slots)

  • Deposits - The number of ETH deposits included in the epoch (validators must stake ETH to become validators)

  • Slashings - Number of penalties given to proposers of blocks or attestors

  • Voting participation - The amount of staked ETH used to attest blocks

  • Validators - Number of validators active for the epoch

  • Average Validator balance - Average balance for active validators

  • Slots - Number of slots included in the epoch (slots include one valid block)\

Slot

Slots are opportunities for block creation, the data available for each slot includes:

  • Epoch - The epoch in which the slot is valid

  • Slot number

  • Status - The status of the slot (Proposed/Missed)

  • Time - The slot timestamp

  • Proposer - The validator that proposed the block for the slot

  • Block root - The hash-tree-root of the BeaconBlock

  • Parent root - The hash of the block that came before

  • State root - The hash-tree-root of the BeaconState

  • Signature

  • Randao reveal

  • Graffiti - A block proposer can include 32 byte long message to its block proposal

  • Execution Data

    • Block hash

    • Deposit count

    • Deposit root

  • Attestations - Number of attestations for the block in this slot

  • Deposits - The number of deposits during this slot

  • Voluntary exits - The number of validators that left during the slot

  • Slashings - Number of penalties given to proposers of blocks or attestors

  • Votes - The validators that voted for the block in this slot

Blocks

Delegated Proof of Stake divides time into slots and epochs. So that means new data!

  • Proposer - The validator that was algorithmically chosen to propose the new block

  • Epoch - The epoch in which the block was proposed

  • Slot - The slot in which the block was proposed

  • Attestations - The number of attestation included in the slot—attestations are like votes that indicate the block is ready to go to the Beacon Chain

\

Validators

Validators are responsible for proposing blocks and attesting to them within slots.

  • Validator number - Unique number that represents the validator

  • Current balance - The validator's balance including rewards

  • Effective balance - The validator's balance that is used for staking

  • Income - The rewards or penalties received by the validator

  • Status - Whether the validator is currently online and active or not

  • Attestation effectiveness - The average time it takes for the validator's attestations to be included in the chain

  • Eligibility for activation - Date (and epoch) when the validator became available to validate

  • Active since - Date (and epoch) when the validator became active

  • Proposed blocks - The block that the validator has proposed

  • Attestations - The attestations that the validator has provided

  • Deposits - The from address, transaction hash, block number, timestamp, amount and status of the staking deposit made by the validator

\

Attestations

Attestations are "yes" votes to include blocks in the chain. Their data relates to a record of the attestation and the validators who attested

  • Slot - The slot in which the attestation took place

  • Committee index - The index of the committee at the given slot

  • Aggregation bits - Represents the aggregated attestation of all participating validators in the attestation

  • Validators - The validators that provided attestations

  • Beacon block root - Points to the block to which validators are attesting

  • Source - Points to the latest justified epoch

  • Target - Points to the latest epoch boundary

  • Signature

Network

The consensus layer top-level data includes the following:

  • Current epoch

  • Current slot

  • Active validators - Number of active validators

  • Pending validators - Number of validators waiting for to be made active

  • Staked HAH - Amount of HAH staked in the network

  • Average balance - Average HAH balance of validators

\

PreviousData and AnalysisNextSmart Contract

Last updated