[Urgent] Polygon Transaction data duplicated and data quality issue

[jensenity]

As you can see at this polygon transactions, you can see that the hash is on 2022-02-09 00:26:21 UTC in 24714823

select
* from `public-data-finance.crypto_polygon.transactions`
where TIMESTAMP_TRUNC(block_timestamp, hour) = TIMESTAMP_TRUNC("2022-02-09 00:00:00", hour)
    AND `hash` = "0xd481ff0f96cdea342e8baa7d3ca65d59589cdec2782b0b7b4f65731bfae0e63e"
    ;

But when you look at https://polygonscan.com/tx/0xd481ff0f96cdea342e8baa7d3ca65d59589cdec2782b0b7b4f65731bfae0e63e
The transaction happened in Feb-09-2022 12:34:55 AM +UTC

So we deep dive into the logs, we found the transaction is logged in two different blocks and two different block timestamp as well.

select
    *
from `public-data-finance.crypto_polygon.transactions`
where TIMESTAMP_TRUNC(block_timestamp, hour) >= TIMESTAMP_TRUNC("2022-02-09 00:00:00", hour)
    AND `hash` = "0xd481ff0f96cdea342e8baa7d3ca65d59589cdec2782b0b7b4f65731bfae0e63e"

but we couldn't find the transaction in https://polygonscan.com/txs?block=24714823 at all.

Can anyone help deep dive in this more?

[araa47]

This seems like a forked block likely caused due to the following fork in the network

https://polygonscan.com/block/24714822/f

It will be automatically removed when our sync runs

[jensenity]

@araa47 can u elaborate more on this? We waited more than 10 hours for the sync to happen but the results are still the same. When is the sync? And what's going to change after the sync? Can we expect the same results from polygonscan?