It seems like 0xA9D1e08C7793af67e9d92fe308d5697FB81d3E43 is not verified and also input data on 0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a may contains the tuple so it will be hard to try to analyze it's input data.

Who knows, the developer don't want to share it so can make it more difficult to analyze than normal.

But there's one thing that the developer can not change.

It's the transfer event on ERC-20 contract and developer must call transfer function on ERC-20 and this transfer function emit Transfer event.

You can check about these transfers on https://etherscan.io/tx/0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a#eventlog .

You can see how to do it pragmatically on here. How do I parse the transaction receipt log with web3.js?

Thanks.

It seems like 0xA9D1e08C7793af67e9d92fe308d5697FB81d3E43 is not verified and also input data on 0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a may contains the tuple so it will be hard to try to analyze its input data.

Who knows, the developer don't want to share it so can make it more difficult to analyze than normal.

But there's one thing that the developer can not change.

It's the transfer event on ERC-20 contract and developer must call transfer function on ERC-20 and this transfer function emit Transfer event.

You can check about these transfers on https://etherscan.io/tx/0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a#eventlog .

You can see how to do it pragmatically on here. How do I parse the transaction receipt log with web3.js?

Thanks.

It seems like 0xA9D1e08C7793af67e9d92fe308d5697FB81d3E43 is not verified and also input data on 0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a is contains the tuple so it will be hard to try to analyze it's input data.

Who knows, the developer don't want to share it so can make it more difficult to analyze than normal.

But there's one thing that the developer can not change.

It's the transfer event on ERC-20 contract and developer must call transfer function on ERC-20 and this transfer function emit Transfer event.

You can check about these transfers on https://etherscan.io/tx/0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a#eventlog .

You can see how to do it pragmatically on here. How do I parse the transaction receipt log with web3.js?

Thanks.

It seems like 0xA9D1e08C7793af67e9d92fe308d5697FB81d3E43 is not verified and also input data on 0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a may contains the tuple so it will be hard to try to analyze it's input data.

Who knows, the developer don't want to share it so can make it more difficult to analyze than normal.

But there's one thing that the developer can not change.

It's the transfer event on ERC-20 contract and developer must call transfer function on ERC-20 and this transfer function emit Transfer event.

You can check about these transfers on https://etherscan.io/tx/0x5ed78dc97ed6c4a3797be99f04977bbcfd45ca5c0ae97ade16dce69e7ecc558a#eventlog .

You can see how to do it pragmatically on here. How do I parse the transaction receipt log with web3.js?

Thanks.