Let's take a look at this tx:


as you can see it's buying token through pancake swap:


however input data looks like this


from which we can easily work out (according to 100s of identical transactions with dynamic address argument) that this is the address that's passed to the contract function:


however these contract addresses do not match. Is this some default Solidity argument encoding? is there any way to decode this?

1 Answer 1


The target contract (0x890308ccaeb490a536ee70230f9183524b17f082) isn't the official pancake swap contract. The contract isn't verified so it can be a a completely different contract that uses its own api and the parameter can be anything.

Don't assume a contract will do something from the transaction input alone. A contract can do anything.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.