You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
Looking into the data generated by the BNB node for Kafka output, I found something strange. The data from the transactions and what I see in API responses do not match. For example, for tx BCD1E9DA0D58C9B08DAA0CEEF0CA3A01E62C62F0647B89E214453DB6A6B81E4D in block 179998840, the data generated on Kafka looked like this:
Looking into the data generated by the BNB node for Kafka output, I found something strange. The data from the transactions and what I see in API responses do not match. For example, for tx BCD1E9DA0D58C9B08DAA0CEEF0CA3A01E62C62F0647B89E214453DB6A6B81E4D in block 179998840, the data generated on Kafka looked like this:
However, if we look at https://dex.binance.org/api/v1/transactions-in-block/179998840, we see that for this tx:
Note the fee is zero, and data has different fields. So I wonder, why the tx fee is different here? https://api.binance.org/bc/api/v1/blocks/179998840/txs also says the fee is zero. Which data is correct?
The text was updated successfully, but these errors were encountered: