Inaccurate transaction address returned by Bitquery as compared to Etherscan

GraphQL API
1

The GraphQL query for the same has been listed as follows Jira Request Sayon #1

The transaction addresses are as follows:-

  1. 0x837dc41856c752e1b955c27381df768acf680bb7
  2. 0xe8dbddcb472073e718f73faa61567cb986dd7888
  3. 0xe1d84ba0f002315fbb60ebf7b59ed959f3053ca8

For txAddress 0x837dc41856c752e1b955c27381df768acf680bb7 the count returned by Bitquery is 63 while Etherscan.io returns 73.

For txAddress 0xe8dbddcb472073e718f73faa61567cb986dd7888 the count returned by Bitquery is 7 while Etherscan.io returns 8.

For txAddress 0xe1d84ba0f002315fbb60ebf7b59ed959f3053ca8 the count returned by Bitquery is 16 while Etherscan.io returns 20.

Corresponding Jira ticket Log in with Atlassian account