# BSC blocks behind

**URL:** <https://community.bitquery.io/t/bsc-blocks-behind/104>\
**Category:** GraphQL API\
**Tags:** closed\
**Created:** [June 2, 2021, 7:33am UTC](https://community.bitquery.io/t/bsc-blocks-behind/104 "2021-06-02T07:33:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattblack](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mattblack](https://community.bitquery.io/u/mattblack)\
**Post date:** [June 2, 2021, 7:33am UTC](https://community.bitquery.io/t/bsc-blocks-behind/104/1 "2021-06-02T07:33:05Z")

</div>

Hi,

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

```auto
{
  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:

```auto
{
  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](http://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

---

<div class="post-metadata">

**Author:** ![mattblack](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mattblack](https://community.bitquery.io/u/mattblack)\
**Post date:** [June 2, 2021, 7:39am UTC](https://community.bitquery.io/t/bsc-blocks-behind/104/2 "2021-06-02T07:39:58Z")

</div>

After reading around the forum some more, I found this: [https://bloxy.info/status](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?

---

<div class="post-metadata">

**Author:** ![gaurav](https://avatars.discourse-cdn.com/v4/letter/g/b487fb/32.png) [@gaurav](https://community.bitquery.io/u/gaurav)\
**Post date:** [June 2, 2021, 12:19pm UTC](https://community.bitquery.io/t/bsc-blocks-behind/104/3 "2021-06-02T12:19:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![mattblack](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mattblack](https://community.bitquery.io/u/mattblack)\
**Post date:** [June 4, 2021, 1:00pm UTC](https://community.bitquery.io/t/bsc-blocks-behind/104/4 "2021-06-04T13:00:55Z")

</div>

Okay thanks, looking forward to that.