I am trying to get all transfers of specific NFT collection (url: https://deep-index.moralis.io/api/v2/nft/0xFfa60CD831374F40358de1aA0489123935a8287D/trades?chain=eth&format=decimal). The problem i am fasing is that when there is a multiple token transfer in one transaction hash and there is NFT from different collection it gets market with the token address of the token that i am trying to pull data. Example transaction_hash: 0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca (https://etherscan.io/tx/0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca ), has 3 tokens in it, 2 (TokenID[1141], TokenID[3438])of the collection that i trying to pull data and TokenID[2949] from different collection, it should either be flagged with its real token address (0x8460BB8EB1251a923A31486af9567E500Fc2f43f) or not included in the list, but in the data i am getting all of three tokens have the same token address.
Hi @stef
I tried testing the tx hash with get decoded transaction endpoint. I could see the correct data when I use this endpoint.
This is the request URL
https://deep-index.moralis.io/api/v2/transaction/0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca/verbose?chain=eth
In the response, I could see each token transfer with its own token address.
Can you check the data again?
Or if I am missing something please let me know.
Thanks
Hi @johnversus,
I am intrested in transfers of an NFT collection and when i use this url: https://deep-index.moralis.io/api/v2/nft/0xFfa60CD831374F40358de1aA0489123935a8287D/trades?chain=eth&format=decimal , it sets all the the tokens address to the one that i am searching for, even thou that some of them are from other collections( have different token address). Don’t know why it even includes them. I have give this transaction hash only as an exsample.
Ahh Yeah I see it now. The token address in the below object is shown incorrect for 1141 and 3438.
Will share it with the devs and let you know of any updates here. Thanks
{
"transaction_hash": "0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca",
"transaction_index": "77",
"token_ids": [
"2949"
],
"seller_address": "0x47f3f73d112f825e7154251b143b30a49bfe7522",
"buyer_address": "0xa7a9f8755db6f69af33f86fdcee95292d8d78498",
"token_address": "0xffa60cd831374f40358de1aa0489123935a8287d",
"marketplace_address": "0x00000000006c3852cbef3e08e8df289169ede581",
"price": "10000000000000000",
"price_token_address": null,
"block_timestamp": "2023-02-25T10:54:47.000Z",
"block_number": "16704837",
"block_hash": "0xa2c6faf4c6c580b48f0d62c39faa0aa5b4fcc15667a293542ecdba4b5fb56e31"
},
{
"transaction_hash": "0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca",
"transaction_index": "77",
"token_ids": [
"3438"
],
"seller_address": "0x47f3f73d112f825e7154251b143b30a49bfe7522",
"buyer_address": "0xa7a9f8755db6f69af33f86fdcee95292d8d78498",
"token_address": "0xffa60cd831374f40358de1aa0489123935a8287d",
"marketplace_address": "0x00000000006c3852cbef3e08e8df289169ede581",
"price": "70500000000000000",
"price_token_address": null,
"block_timestamp": "2023-02-25T10:54:47.000Z",
"block_number": "16704837",
"block_hash": "0xa2c6faf4c6c580b48f0d62c39faa0aa5b4fcc15667a293542ecdba4b5fb56e31"
},
{
"transaction_hash": "0xa87334f85771210a063001fe6f89cec6b627fc33b2c8e48ef00cfc0b8bd2a5ca",
"transaction_index": "77",
"token_ids": [
"1141"
],
"seller_address": "0x47f3f73d112f825e7154251b143b30a49bfe7522",
"buyer_address": "0xa7a9f8755db6f69af33f86fdcee95292d8d78498",
"token_address": "0xffa60cd831374f40358de1aa0489123935a8287d",
"marketplace_address": "0x00000000006c3852cbef3e08e8df289169ede581",
"price": "67900000000000000",
"price_token_address": null,
"block_timestamp": "2023-02-25T10:54:47.000Z",
"block_number": "16704837",
"block_hash": "0xa2c6faf4c6c580b48f0d62c39faa0aa5b4fcc15667a293542ecdba4b5fb56e31"
},
don’t know if it matters, but the token 2949 is the one with wrong token address
Hi @stef
Sorry for the delay. This seems not yet resolved. I have pushed this issue to the devs again. Will let know soon if there is an update from the devs.
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.