useFetchBlocks hooks refactor

[portdeveloper]

Description

Solves #528 . Also I have added wallet and test actions to the client with the websocket connection.
I removed the isLoading state too, because it already is loading so fast with wss, using that isLoading state actually makes the experience worse.
I plan to optimize and make the code for useFetchBlocks a little bit better before merging. Feel free to correct me and share your ideas!

Additional Information

• I have read the contributing docs (if this is your first contribution)
• This is not a duplicate of any existing pull request

Related Issues

_Closes #528 _

Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.

Your ENS/address: portdev.eth

[technophile-04]

Tysm @portdeveloper, this is looking great !! Added very minor comments

But everything looks and works great !!

---

Also noticed that yarn fork does not show any transactions on blockexplorer now, it was used to show things earlier if you wait a lot as mentioned in this #528 (comment) video

I think its because now we are using websockets and if you inspect chrome developers tools network tab I see bunch of "canceled" eth_blockNumber request when you yarn fork and go to blockexplorer page but not completely sure if its because of websockets

Nevertheless, I think these changes work great on Localchain and almost ready to merge 🙌

[portdeveloper]

Thanks @technophile-04 for your valuable feedback. I have fixed the things you have pointed out. After this is merged I will look into test actions so that the users can have a more fine grained control over their local environment. yarn fork is an issue too. I have tested it myself with a websocket connection to infura and the problem is that the useFetchBlocks, with its current logic, tries to get all blocks and all transactions in them before showing any.

[technophile-04]

Thanks @portdeveloper, I think it looks and works great now!

After this is merged I will look into test actions so that the users can have a more fine grained control over their local environment. yarn fork is an issue too. I have tested it myself with a websocket connection to infura and the problem is that the useFetchBlocks, with its current logic, tries to get all blocks and all transactions in them before showing any.

Yup, it would be really helpful if we could fix that so we only make requests for the latest 20 blocks and fetch their corresponding tx receipts & details that's it we shouldn't make request for other blocks, I will create an issue for this 🙌

But thanks for this PR always appreciate it !!