-1

There are few blocks in near which are missing in mainnet but present in testnet and it shows as testnet specific blocks. Please suggest how do we consider these blocks or get these blocks using the api "https://archival-rpc.mainnet.near.org". Below is the scenario for one of the block

If I try to get the block details of the block 73685420 by using the below curl query:

curl --location --request POST 'https://archival-rpc.mainnet.near.org' \
--header 'Content-Type: application/json' \
--data-raw '{
  "jsonrpc": "2.0",
  "id": "dontcare",
  "method": "block",
  "params": {
    "block_id": 73685420
  }
}'

I get the below output

{
    "jsonrpc": "2.0",
    "error": {
        "name": "HANDLER_ERROR",
        "cause": {
            "info": {},
            "name": "UNKNOWN_BLOCK"
        },
        "code": -32000,
        "message": "Server error",
        "data": "DB Not Found Error: BLOCK HEIGHT: 73685420 \n Cause: Unknown"
    },
    "id": "dontcare"
}

But when I searched the above block in testnet explorer I was able to get it.

how to get the details from mainnet?

Testnet Explorer Block

James Z
  • 12,209
  • 10
  • 24
  • 44
Swornatoya Lenka
  • 11
  • 1
  • 4

1 Answers1

0

maybe you can find the answer here: Why Blocks are Missing or Skipped on NEAR

Just a little explanation about the info inside the link:

The blocks are very fast in NEAR Protocol, and the transactions should resolve quickly, sometimes is the specifict validator answer late the block is skipped and the transactions resolved in next, this works as expected.

But thats the reason of the skipped blocks.

Juan Peña
  • 81
  • 1
  • 3