[SOLVED] Is there a problem with web3 API now?

Hi, I’m using this endpoint:https://deep-index.moralis.io/api/v2/block/{block_number_or_hash}/nft/transfers

And I’m getting this message for most blocks:
{
ā€œmessageā€: ā€œNo block foundā€
}

I checked the Moralis status and it says it’s online.

It is working for me.

for which block number it is giving this error and what is the chain name?

This block number 15873257 (and others), it’s on ethereum chain

In my case it returns the above message for most recent blocks (within one minute from now). There is no problem getting the older blocks (>1 min).

I guess some delay is expected while getting the data from the new blocks. You can use a delay or retry in case of such error.

Yeah but that wasn’t the case before, and I’ve been using this API for months now. It started happening today… Is it something new?

I’ll have to check. I don’t know of a recent change that would affect this.

Thank you, please let me know if you find something

this syntax seems to work now:

https://deep-index.moralis.io/api/v2/nft/transfers?chain=eth&from_block=15874127&to_block=15874127&format=decimal

this one works too for me now

https://deep-index.moralis.io/api/v2/block/15874132/nft/transfers?chain=eth&limit=100

you are still seeing that issue?

1 Like

It seems like it works now, thank you!

1 Like