https://fuellabs.github.io/block-explorer-v2/address/0x773d7892d57b964bb6280860083c957a11b9cef733e4760b80e500d437652334

Looks like time is coming incorrect from back-end. It was hidden in front-end in PR #75 , but should be added again after problem is fixed

Summary

As a user I would like to be able to filter the Tx's e.g. by a time range, address, interaction type, amount etc.
There aren't many fields there atm (ref screenshot) but more tags may be tracked and then used to filter

Screenshot

Bring up to speed on breaking changes. We need this done for testnet release, since we need a block explorer.

blocked by deploy of the testnet on a public domain

E.g. clicking on the witness index of an input should go to the indexed witness, and maybe highlight the box for that witness. Same for input index of a contract output. Should apply to anything linked.

if we can either display the proper gas used in the block-explorer-v2, or just remove it.

Move beta-1 as a saved endpoint.

A number of fields have been added to txs, including initial storage slots and byte price. Add all missing fields.

Inputs, don't distinguish coin vs predicate spends. If an input has no predicate code or data, then just hide those fields.

Changing env prop GRAPHQL_API_ENDPOINT is not working if you have accessed the project previously, unless you clear localStorage data.

This code is causing it:

I think we should remove this code using API url saved in localStorage, unless I'm not seeing the use case for it

@luizstacio you see any problems on removing it?

Ref: #76

Q: Can we include something similar to gasUsed in the GraphQL API?

The schema of fuel-core GraphQL API returns only the gasPrice and the gasLimit of a Transaction. We need to display the transaction fee in the UI which would be something like gasPrice * gasUsed

Add a little (i) ("i" in a circle) or (?) next to each transaction field that, when hovered over, provides more information on what that field is.

https://etherscan.io/tx/0xdae14278a1af5244b64b5b1efca075bfb3aa6b49c2267f061b9d664f8230e005

It should build and run the project in a subfolder to make sure that the version to be deployed on gh-pages didn't break;

The environment for this test should be;

PUBLIC_URL: "/block-explorer-v2"
REACT_APP_GRAPHQL_API_ENDPOINT: "https://dubai.swayswap.io/graphql"

Rename coin to asset ID

Create a mechanism to have static pages for each fuel-core version

Summary

The explorer is limited to 10 Tx's. Pagination should be added to allow the user to view all of their Tx's. This is especially important since the Tx's are in the incorrect order atm. Ref #92

Screenshot

Summary

When a Tx is made it gets added to the Tx section at the bottom of the screen.
The problem is the order that it is added in is incorrect.
It currently leaves the oldest Tx at the top and the latest Tx at the bottom so if you want to see your latest Tx's you must scroll all the way down (and potentially switch via pagination if enough Tx's happen).

Change the order to have the latest Tx be at the top.

Screenshot

The address page includes a "Coins" in the top-right, but it's not clear what that means. UTXOs? Distinct assets?

I know we don't currently have help hovers, but until we do it may be worth it to just hide.

Allow it to search for Transaction / Address

It should be possible to search by fuel... address. Using search or accessing the page '/address/fuel...'

Q: Is there a way to sort transactions by time?

On the homepage of the explorer we need to display the latest transactions.
It seems that the current implementation of the fuel-core GraphQL API returns the transactions sorted by id ⬇️

query GetHomeTransaction { 
  transactions(last: 5) {
    edges {
      node {
        id
        status {
          __typename
          ... on SubmittedStatus {
          	time
        	}
          ... on SuccessStatus {
          	time
        	}
        }
      }
    }
  }
}

{
  "data": {
    "transactions": {
      "edges": [
        {
          "node": {
            "id": "0x9a2d3313c7094b92ff0db567d885afa2c8715bd37561133caeeb2814cedcd9c4",
            "status": {
              "__typename": "SuccessStatus",
              "time": "2021-10-16T22:37:58.398421+00:00"
            }
          }
        },
        {
          "node": {
            "id": "0xb18249c26287c1ef6a137b2049d5e6f533d339ada9c7c0bce9f2c4a2aef72aff",
            "status": {
              "__typename": "SubmittedStatus",
              "time": "2021-10-16T22:52:03.083460+00:00"
            }
          }
        },
        {
          "node": {
            "id": "0xb56f197b4cfe2be75755ab51c199a07c0706a4997dcd0326e32f72f593b2a691",
            "status": {
              "__typename": "SuccessStatus",
              "time": "2021-10-16T22:56:25.717232+00:00"
            }
          }
        },
        {
          "node": {
            "id": "0xceb9d709f2d1ee57b13a5925cd0decdbcab20e9f68892362ae0187334bffc12a",
            "status": {
              "__typename": "SubmittedStatus",
              "time": "2021-10-16T21:55:32.358434+00:00"
            }
          }
        },
        {
          "node": {
            "id": "0xd1863025aa7408a30d733d704dfb798dcf8b7dfca3e289660f33e7da50c63f60",
            "status": {
              "__typename": "SuccessStatus",
              "time": "2021-10-16T22:58:35.213025+00:00"
            }
          }
        }
      ],
    }
  }
}

Change github page fuel-core node to https://node.swayswap.io/graphql

Q: Is there a way to force 2 transactions to be included in the same block?

I tried to send a request to fuel-core GraphQL API with this mutation in order to make the submit calls as close as possible

mutation Mutation($tx1: String!, $tx2: String!) {
  first: submit(tx: $tx1)
  second: submit(tx: $tx2)
}

The transactions were mined in the same second, but included in 2 different blocks.

Integrate Semantic Release for automating the release process. Git tags, version number, releases, changelog file edits, all of them will be handled automatically by parsing the commit messages which will to follow a specific format

The current dark-with-dark-green theme isn't the most pleasing. We should have a light theme by default.

The Account Page will display the transactions of a particular account. This means that the fuel GraphQL API needs to allow filtering the query transactions by account address. This was already discussed, just adding it here for tracking

On the latest version of the fuel-core v0.14.0, some queries were changed to different data and function names.

There's no reason to show e.g. a contract created output in the "to" column of the tx list

blocked by the update of the faucet deployment

For decimal numbers (especially gas price) comma-separate on thousands.

• It's possible to use formatUnits and parseUnits from ethers lib.
• Use 3 decimal units
  Refs.: FuelLabs/swayswap#81

Examples:

Header links are specific to a hosted webpage, not a generic block explorer. The links can be added in a branded fork.

Whenever we have a cut address, add a "copy to clipboard" button.

Example:

Currently, script and create txs are only distinguished by their text. Should distinguish them with different colors. Even two shades of the same color.

We need to wait for the endpoint name: https://github.com/FuelLabs/pm/issues/13

This is the current block due to wallet requirement;

• Connect wallet
• Execute transaction
• Deploy contract
• Call functions using method generated interface

Contract created outputs now feature an initial storage root. If it's non-default, then it should be shown.

Hashes and larger fields (e.g. witnesses) should have a clipboard icon next to them that copies them.

See https://etherscan.io/tx/0xdae14278a1af5244b64b5b1efca075bfb3aa6b49c2267f061b9d664f8230e005 how it has a clipboard icon next to tx hash

Examples

• Remove link from coins
• Remove link from contracts
• Fix numbers on the detail transactions page
• Fix numbers on the address page
• Remove Fee(USD) address page
• Remove "Ethereum block number" and "Number of addresses" on the block page
• Fix "to", "value", "coin" and remove "fee (USD)" on the Block transactions list.

Today is already possible to switch the providerUrl would be good to enable this to be set via query param.

The gas price as of #80 only accounts for base coin decimals, but not the gas price factor. The resultant value needs to be further divided by the gas price factor.

Tricky: this will be a very small number, e.g. 10^-15.