404 page for not found Block.

[blockscout]

404 page for not found Block.

[acravenho]

😆 "Easy Cowboy! This block doesn't exist yet!"

[gfreh]

@acravenho I've updated the description and added a suggestion for the block details page in the scenario described by this issue. WDYT?

I've also left a question.

[acravenho]

@gfreh I think that looks good. I'm not sure I understand the question. As far as differentiating the design, yes, we should have the design different so the user knows this block doesn't really exist yet.

[gfreh]

@acravenho By differentiating, I mean having a different message when the block is in the past, but we haven't indexed it yet vs. when the block is in the future. Not sure if that makes sense, though 😅

[acravenho]

🤔 Yes, you're right. That would make sense. It's pretty easy and inexpensive to run the query for the tip of the chain. If below the tip we should provide the exact message that you have above.

[gfreh]

Nice! Do you have a suggestion for the message in the case the block number is above the tip?

[w-sanches]

I'll work on this one

[w-sanches]

@acravenho If i'm trying to access a not-indexed block by its hash, should I show that the block is not processed yet or that it does not exist?
I don't know if I can check if that hash is in the past or the future.

Example: https://blockscout.com/poa/core/blocks/0xf511fffa6403456a120edda6e1984a21e99ef2ca580f02f5367abc59bf16cddc/transactions