Just as a hint, because thats how I figured out to do it:
If the internal transaction is causing an event, you can use the moralis endpoints to fetch all events of the contract that causes the transaction. I am using this on BSC and it works fine. However, it might need some tricky tries since you need to provide the ABI json for the event in question. I cannot see it in your example, so I am not sure if this hint really works for you.
I don’t know when it will be added. But if you want to listen the only contract for these transactions you can easily open input of the transaction and you will see the receipint address there:
Would like to +1 this thread. We’d like to retrieve internal transactions using the Moralis API. For example, the following transaction has an internal transfer of 187.99 MATIC --> WMATIC which is not captured as an ERC20 transfer, therefore not reported in the Moralis API getTokenTransfers().
We need to capture these transfers because our dapp analyzes deposits into liquidity pools. In this case, the deposit consists of one ERC20 token (PolyDoge) and MATIC. Without capturing internal transfers, our code can only see half the deposit.
Please let us know when Moralis would include this functionality. And in the meanwhile, would appreciate any workaround ideas.
it looks like this is the event associated with that transaction:
Address 0x0d500b1d8e8ef31e21c99d1db9a6444d3adf1270
Name Transfer (index_topic_1 address from, index_topic_2 address to, uint256 value)View Source
Topics
0 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
1 0xc0788a3ad43d79aa53b09c2eacc313a787d1d607
2 0x5d9d66ac0db91ec463fb3e9e5b1513dbff02fd0f
Data
value : 187997251356272809277
Thanks. I’m not super familiar with events. Are you suggesting to use them as a workaround? Will internal transactions always have an event associated with them?