BSC blocks behind

Hi,

When I query the BTC blockchain or ETH blockchain to get the latest block count, e.g. with this query

{
  ethereum {
    blocks(options: {limit: 1, desc: "height"}) {
      height
      transactionCount
      date {
        date,
      }
    }
  }
}

I get the latest block just fine for BTC/ETH.

However, when I try to do the same for BSC (Binance Smart Chain), it’s always around 40-50 blocks behind:

{
  ethereum(network:bsc) {
    blocks(options: {limit: 1, desc: "height"}) {
      height
      transactionCount
      date {
        date,
      }
    }
  }
}

At moment of writing, this gives me a block height of 7939709 compared to 7939747 on bscscan.com.

I want to use Bitquery API for real time price updates of BSC tokens via swap exchanges, but because this always laggs a few minutes behind, it’s unusable for me.

Am I querying this correctly? Or is this a known issue?

Thanks

After reading around the forum some more, I found this: https://bloxy.info/status

Apparently almost every blockchain is lagging behind by a few minutes. Doesn’t this make Bitquery unusable for realtime data applications? Is there any solution to this?

We have this delay because we build our architecture for fork resistant, so we only process confirmed blocks, however we are building a real-time system which will be live next quarter.

2 Likes

Okay thanks, looking forward to that.