Block_number_minted may be incorrect in the result of evm api /nft/{address}

Hi

Iā€™m using below endpoint to get the all NFTs via contract address

https://deep-index.moralis.io/api/v2/nft/0x2d71f49a182f11e0bfded70fad48844704051ac9?chain=eth&format=decimal

result

{
      "token_hash": "d9b59fb0063643fa7f406479c1269c95",
      "token_address": "0x2d71f49a182f11e0bfded70fad48844704051ac9",
      "token_id": "23",
      "block_number_minted": "14229888",
      "amount": "1",
      "contract_type": "ERC721",
      "name": "CatArtMuseum",
      "symbol": "CATART",
....

And then Iā€™m using nft transfer api to get the transaction hash of mint for the NFT.

https://deep-index.moralis.io/api/v2/nft/0x2d71f49a182f11e0bfded70fad48844704051ac9/transfers?chain=eth

result

    {
      "block_number": "14229889",
      "block_timestamp": "2022-02-18T11:38:52.000Z",
      "block_hash": "0x02b1eddccac075ae9c28e6bae68f6cbcdf3e91e6c1f974ca65ffac3e78e530eb",
      "transaction_hash": "0x8cce28010035f6371744db8ca600e2e631d8a4fede4444efbbbbc75c71e62301",
      "transaction_index": 62,
      "log_index": 96,
      "value": "0",
      "contract_type": "ERC721",
      "transaction_type": "Single",
      "token_address": "0x2d71f49a182f11e0bfded70fad48844704051ac9",
      "token_id": "23",
      "from_address": "0x0000000000000000000000000000000000000000",
      "to_address": "0xbd1802a50ba9c621e929282e45b1bb860c33714c",
      "amount": "1",
      "verified": 1,
      "operator": null,
      "possible_spam": false
    }

As above two result, the block_number_minted in the result of evm api /nft/{address} is 14229888, but the block_number in the result of /nft/{address}/transfers is 14229889 when from_address=0x00 and token_id=23.

After checking with etherscan, it was found that the correct one should be 14229889.

https://etherscan.io/tx/0x8cce28010035f6371744db8ca600e2e631d8a4fede4444efbbbbc75c71e62301

Hi @jack_lu

Thanks for reporting. We shared the details with the team. Will let you if there any update.

Is there any update on this issue?

Hi @jack_lu

As of now, we dont have any update on this issue. We will update you soon as soon as we receive any updates.

Thank you for your patience.