Loading chain data
Paste calldata and see its structure: the 4-byte selector, then every 32-byte word behind it with the readings that hold without knowing the function.
This is a structural decode, not a semantic one. Without the contract ABI there is no way to know that word 0 is a recipient and word 1 is an amount, so nothing here claims to. Dynamic types make it harder still: a word holding 32, 64 or 96 is usually a byte offset into the tail rather than a quantity, and arrays and strings are laid out further down. Read the readings as possibilities, not as facts.
For a decode with real parameter names, open the transaction on this site. Verified contracts get their arguments named from the ABI on the transaction pages.
Hex, with or without the 0x prefix.
Need to read a value out of one of those words? The unit converter turns it into ether or gwei without rounding.