Ethereum Esterscan API returns the internal transaction, despite the simple transfer application
As a developer of Ethereum, we tested the API etterscan to collect information about blockchain transactions. However, we face a situation in which API returns a single internal transaction for a simple transfer application, despite the main logic that implies that there should be no such transaction.
Details of the transaction
The transaction in question is as follows: 0x33E0DAB83AA27BA8B2A08B3C69D61A34911A4ADB6E7A35DDDDD3CF11383FCCC3. This transaction seems to be a simple transfer of the gala, from the sender’s portfolio (address 0x33e0dab83a27ba8b2a08b3c69d61a3491a4adb6e7a35cf11383f43fc3))
Etherean execution
After reviewing the details of the transaction in Eserscan, we noticed that an internal transaction was indicated: 1. This may seem contrasting at first glance, since it seems to show an additional transaction associated with the original 0x33E0DAB83AAAA2BA8B2A08B3C69D61A3491A4ADB6E7A35DDDDD3C11383FC3`However, this internal transaction is not really related to the application for simple transfer.
API response
According to API Esterscan documentation, internal transaction can be returned to certain types of transactions, such as:
- 1 TERNED ETHER’
0x00000000000000000000000000000000000000000000(gas block)
0X0000000000000000000000000000000000000000000000000000000000000000000000000GAS COSTS)
In this case, the internal transaction probably returns due to the logic1 ether. The API documentation does not explicitly establish that the internal transaction can be returned for simple transfer applications, which has led to our initial confusion.
Conclusion
While API Etterscan can return an internal transaction for a regular transfer application, it seems that it incorrectly interprets transaction data. This number emphasizes the importance of a careful review of the API documentation and the understanding of the main logic behind several types of transactions. As developers, we must ensure that our evidence and requests precisely reflect the expected behavior of Eserscan.
Sample code
As a reference, here is an example of fragment of code in solidity (Ethereum), which demonstrates a simple transfer application:
`Soliditude
Pragma solidity ^0.8.0;
Simplero contract {
Functional transfer (slogan in the address) public {
// Do the transfer logic here ...
// ...
}
}
`
This contract includes a transfer function that allows us to simulate a simple gala tokens transfer between two wallets.
I hope this article helps to clarify any confusion related to the return of the ETSCAN API about internal transactions.