# Network: bsc inbound-outbound queries (including "Money Flow" webpage) fail 99% of the time

**URL:** <https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956>\
**Category:** GraphQL API\
**Tags:** closed\
**Created:** [April 3, 2022, 10:44am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956 "2022-04-03T10:44:46Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 3, 2022, 10:44am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/1 "2022-04-03T10:44:47Z")

</div>

Hi,

for the last week, I’ve been struggling to get the money flow of a specific wallet for a specified date range (inbound-outbound). **Important notice:** this started happening to me a month or two ago. Before that, it worked fine without serious issues.

**First:**  
The **Money Flow** pipe diagram (Sankey) basically now doesn’t show/load for me 99% of the time (succeded only once in the last week), not even for the last 7 days range. Example:

> **[0x7BE5916Ca402BfDD10f83cafe0B063E5adA4A506 money flow in Binance (BNB) Smart...](https://explorer.bitquery.io/bsc/address/0x7BE5916Ca402BfDD10f83cafe0B063E5adA4A506/graph)**
>
> Money Flow by address 0x7BE5916Ca402BfDD10f83cafe0B063E5adA4A506 activity in Binance (BNB) Smart Chain Mainnet, statistics of token exchanges

**Second:**  
Based on a query of the Money Flow pipe diagram, mentioned above, I’ve taken the query and stripped it down a bit to watch only BNB flow. It worked fine a few months ago. Now it fails 99% of the time **but still consumes 2-10 points (!)**.  
Link to my query (IDE): [GetAddressIncomeOutcomeBNB\_V2](https://graphql.bitquery.io/ide/GetAddressIncomeOutcomeBNB_V2)

I’ve tried also using the query mentioned in this post (see " **All inbound and outbound transfers for Ethereum**"):

> [@Bitquery's Transfer APIs](https://community.bitquery.io/t/bitquerys-transfer-apis/889):
>
> A blockchain is a peer-to-peer network of computers or servers known as “nodes” that both participate and monitor the transfer of information and assets. Every transfer is recorded on each user’s computer (node), generating a platform of trust based on several identical copies of the ledger. [Bitquery’s](https://bitquery.io/) tools and widgets allow you to query the token transfers for Smart contract chains like Ethereum, Binance, Tron, Matic and Klaytn, Tron, and other Bitcoin Platform Explorers like Bitcoin mainnet a…

I’ve noticed that for Ethereum blockchain works perfectly also for me. However, if I switch to the BSC blockchain (network) and of course enter a wallet from BSC it starts failing immediately, as discussed above.  
Link to my query (IDE): [GraphQL IDE](https://graphql.bitquery.io/ide/GetAddressIncomeOutcome_fromPost)

A few errors I am getting:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/bitquery/original/1X/0aa937144896c982204dcec88042bc1a381ac735.png)

 ![image](https://us1.discourse-cdn.com/flex016/uploads/bitquery/original/1X/101d88cd3867c55300c0dbc6bea356ec4f528a96.png)

Were there changes in BitQuery support for BSC?  
Any feedback on that matter would be welcome.

Kind regards,  
PM

---

<div class="post-metadata">

**Author:** ![aman](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@aman](https://community.bitquery.io/u/aman)\
**Post date:** [April 3, 2022, 2:54pm UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/2 "2022-04-03T14:54:03Z")

</div>

The query could be optimized by breaking it into 2 queries one for inbound and outbound.

> **[bscinboundquery](https://graphql.bitquery.io/ide/bscinboundquery)**
>
> Bitquery is analytical engine for blockchains

The link for the query you shared might be saved in private that’s why we cannot review the query.

---

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 3, 2022, 5:34pm UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/3 "2022-04-03T17:34:37Z")

</div>

Sorry, I was sure that I’ve set it as public:

> **[GraphQL IDE](https://graphql.bitquery.io/ide/GetAddressIncomeOutcome_fromPost)**
>
> Bitquery is analytical engine for blockchains

Will splitting this query into two queries really decrease both **time** and **CPU resources**?

Shouldn’t it perform fine just as it does for the Ethereum blockchain instead?

---

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 4, 2022, 3:42pm UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/4 "2022-04-04T15:42:09Z")

</div>

Splitting to two queries, one for inbound and the second for outbound, did not help at all. Errors still persist when dealing with BSC blockchain/network.

---

<div class="post-metadata">

**Author:** ![mbajpai](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@mbajpai](https://community.bitquery.io/u/mbajpai)\
**Post date:** [April 17, 2022, 7:09am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/5 "2022-04-17T07:09:39Z")

</div>

The query is still not visible

---

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 17, 2022, 9:00am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/6 "2022-04-17T09:00:24Z")

</div>

Try now? I noticed that the BitQuery GraphQL IDE has some issues saving basically anything…

> **[GraphQL IDE](https://graphql.bitquery.io/ide/GetAddressIncomeOutcome_fromPost)**
>
> Bitquery is analytical engine for blockchains

UPDATE: The setting to set the query as shared doesn’t seem to work for whatever reason no matter what I try…  
Due to that, I guess I am forced to post the full query here, I see no other option:

```auto
{
  ethereum(network: bsc) {
    inbound: coinpath(
      initialAddress: {is: "0xd49555ec28380a84ed93a9f4900046463bdae654"}
      depth: {lteq: 1}
      options: {direction: inbound, asc: "depth", desc: "amount", limitBy: {each: "depth", limit: 10}}
      date: {since: "2022-03-01", till: "2022-03-25"}
    ) {
      sender {
        address
        annotation
        smartContract {
          contractType
          currency {
            symbol
            name
          }
        }
      }
      amount
      currency {
        symbol
      }
      depth
      count
    }
    outbound: coinpath(
      initialAddress: {is: "0xd49555ec28380a84ed93a9f4900046463bdae654"}
      depth: {lteq: 1}
      options: {asc: "depth", desc: "amount", limitBy: {each: "depth", limit: 10}}
      date: {since: "2022-03-01", till: "2022-03-25"}
    ) {
      receiver {
        address
        annotation
        smartContract {
          contractType
          currency {
            symbol
            name
          }
        }
      }
      amount
      currency {
        symbol
      }
      depth
      count
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![aman](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@aman](https://community.bitquery.io/u/aman)\
**Post date:** [April 17, 2022, 6:23pm UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/7 "2022-04-17T18:23:19Z")

</div>

I see no problem as I tested your query it’s working.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/bitquery/original/1X/27455b1641cafc34a106105fdcc8ad24753c395e.png)

---

<div class="post-metadata">

**Author:** ![sayon-bitquery](https://sea2.discourse-cdn.com/flex016/user_avatar/community.bitquery.io/sayon-bitquery/32/522_2.png) [@sayon-bitquery](https://community.bitquery.io/u/sayon-bitquery)\
**Post date:** [April 20, 2022, 4:58am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/8 "2022-04-20T04:58:58Z")

</div>

But it reduces the number of points deducted from your subscription. Aliasing the GraphQL query gets 2 jobs ( in this case ) done using only 1 API call.

---

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 20, 2022, 3:09pm UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/9 "2022-04-20T15:09:32Z")

</div>

> [@Penko\_Mlakar](#):
>
> ```auto
> {
> ethereum(network: bsc) {
> inbound: coinpath(
> initialAddress: {is: "0xd49555ec28380a84ed93a9f4900046463bdae654"}
> depth: {lteq: 1}
> options: {direction: inbound, asc: "depth", desc: "amount", limitBy: {each: "depth", limit: 10}}
> date: {since: "2022-03-01", till: "2022-03-25"}
> ) {
> sender {
> address
> annotation
> smartContract {
> contractType
> currency {
> symbol
> name
> }
> }
> }
> amount
> currency {
> symbol
> }
> depth
> count
> }
> outbound: coinpath(
> initialAddress: {is: "0xd49555ec28380a84ed93a9f4900046463bdae654"}
> depth: {lteq: 1}
> options: {asc: "depth", desc: "amount", limitBy: {each: "depth", limit: 10}}
> date: {since: "2022-03-01", till: "2022-03-25"}
> ) {
> receiver {
> address
> annotation
> smartContract {
> contractType
> currency {
> symbol
> name
> }
> }
> }
> amount
> currency {
> symbol
> }
> depth
> count
> }
> }
> }
> 
> ```

I tried it again, and I got some errors, but the query seems to have succeeded. Then I reloaded the page and the query succeeded fine with no errors.

I suspect that the BitQuery IDE interface didn’t load properly for me and it had an impact on running the query… Or I have some bookmark that I should stop using I guess…

---

<div class="post-metadata">

**Author:** ![sayon-bitquery](https://sea2.discourse-cdn.com/flex016/user_avatar/community.bitquery.io/sayon-bitquery/32/522_2.png) [@sayon-bitquery](https://community.bitquery.io/u/sayon-bitquery)\
**Post date:** [April 22, 2022, 2:47am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/10 "2022-04-22T02:47:28Z")

</div>

So is this issue resolved @Penko_Mlakar or are you facing some difficulties again?

---

<div class="post-metadata">

**Author:** ![Penko\_Mlakar](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Penko\_Mlakar](https://community.bitquery.io/u/Penko_Mlakar)\
**Post date:** [April 22, 2022, 6:28am UTC](https://community.bitquery.io/t/network-bsc-inbound-outbound-queries-including-money-flow-webpage-fail-99-of-the-time/956/11 "2022-04-22T06:28:30Z")

</div>

Yes, I believe this issue can be marked as resolved.  
Thank you for all your help.