Web3 Event api is pulling incorrect data for one block

Technical Issue Reporting
#1

The api does not match the event data as what is shown on etherscan for this particular block. Other blocks are ok.

Example
https://etherscan.io/tx/0x4e1536e5b4eb6c3727981a89583c76f175c6f494f382e79252b9799a91e51681#eventlog

#2

I get this for the transaction:

 "logs": [
    {
      "log_index": "89",
      "transaction_hash": "0x4e1536e5b4eb6c3727981a89583c76f175c6f494f382e79252b9799a91e51681",
      "transaction_index": "78",
      "address": "0x7744bb628f1cee71ea796a80c7c2630260a67e6a",
      "data": "0x000000000000000000000000e4cea415ef71facb434dac76159be0bb5394b7560000000000000000000000000000000000000000000000000214e8348c4f0000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000004a70000000000000000000000000000000000000000000000000000000000000bc5",
      "topic0": "0x50ad76adbb3bc37e53257a9032867f7856f8b500e7eaf97b8ee6d0c5355f0185",
      "topic1": null,
      "topic2": null,
      "topic3": null,
      "block_timestamp": "2022-02-27T00:55:57.000Z",
      "block_number": "14285109",
      "block_hash": "0x3d10676821764f8dc5c824345271976ae25a89e95debbc49ff8fec72aff42ff7",
      "transfer_index": [
        14285109,
        78,
        89
      ]
    }
  ]

what is the difference that you see?

#3

The difference is in the event data. id1 should be 1189.

{'transaction_hash': '0x4e1536e5b4eb6c3727981a89583c76f175c6f494f382e79252b9799a91e51681', 'address': '0x7744bb628f1cee71ea796a80c7c2630260a67e6a', 'block_timestamp': '2022-02-27T00:55:57.000Z', 'block_number': '14285109', 'block_hash': '0x3d10676821764f8dc5c824345271976ae25a89e95debbc49ff8fec72aff42ff7', 'data': {'address': '0xe4cea415ef71facb434dac76159be0bb5394b756', 'amount': '150000000000000000', 'count': '2', 'id1': '1191', 'id2': '3013'}}
#4

ok, got it, 4a5 vs 4a7

how do you know what it the right number from those two?

#5

Etherscan and infura are both showing 4a5. This is the log using infura

{'address': '0x7744bB628f1CEE71ea796A80C7c2630260a67e6A', 'blockHash': HexBytes('0xad8d140dfa3f7d58c6ac99f0596abae00383acc9155d8cdd255bee533fa278f9'), 'blockNumber': 14285109, 'data': '0x000000000000000000000000e4cea415ef71facb434dac76159be0bb5394b7560000000000000000000000000000000000000000000000000214e8348c4f0000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000004a50000000000000000000000000000000000000000000000000000000000000bc5', 'logIndex': 94, 'removed': False, 'topics': [HexBytes('0x50ad76adbb3bc37e53257a9032867f7856f8b500e7eaf97b8ee6d0c5355f0185')], 'transactionHash': HexBytes('0x4e1536e5b4eb6c3727981a89583c76f175c6f494f382e79252b9799a91e51681'), 'transactionIndex': 77}
#6

yes, that seems to be the right number, we’ll have to investigate

#7

Here are some other transactions if that’s helpful

0x095cf2220fc7fbfee1cf56efbc2fab9d2e2d9d2155518a1cbac067f8f7476c9a
0xf572ec53c52d9083a2f1ac0722868d35d8620f5ecf249a80300891f6c326a4f0
0xcb85b1ce42f0440ed4464e071687a02e63de0b50efd36c6185faa3deb4b4c957
1 Like
#8

can you check again now?

#9

Looks correct now, thanks! What was the issue?

#10

it looks like it was some internal problem in our processing