A movement record has a source label, a destination label and an unscaled quantity.
SEE IT FOR YOURSELF
From an emitted Transfer event to a receipt logStep 1 / 4
A token implementation may update balances and emit its standard Transfer event. State and the emitted record are related but distinct.
A token implementation may update balances and emit its standard Transfer event. State and the emitted record are related but distinct.A non-anonymous Transfer event uses the full thirty-two-byte Keccak-256 signature digest as topic zero, not a four-byte function selector.In the common ERC-20 shape, from and to occupy topics one and two. The raw value is a thirty-two-byte data word. Other standards can index fields differently.An application can decode receipt logs under the correct ABI. A matching signature does not establish that an unknown emitter is an honest token.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Confirm the event shape
The common ERC-20 Transfer declaration has indexed from and to addresses and a non-indexed uint256 value. Other event declarations need their own schema.
Recover the address fields
Topic one and topic two contain padded address values. Extract and validate their twenty-byte address portions with a typed decoder rather than guessing from visual spacing.
Interpret the amount carefully
The data word holds a raw integer. Converting it to a human token amount needs trusted decimals information; the Transfer record itself does not supply that metadata.
Keep interpretation tied to evidence
Check the emitting contract and receipt context before describing an economic transfer. A matching log alone does not establish honest balances, token value or finalized inclusion.
Inspect the example
event Transfer(address indexed from, address indexed to, uint256 value)
topic 0: 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef
topic 1: 0x0000000000000000000000000000000000000000000000000000000000000001
topic 2: 0x0000000000000000000000000000000000000000000000000000000000000002
data: 0x0000000000000000000000000000000000000000000000000000000000000064
Toy emitter; from address 1; to address 2; raw amount 100.
No token decimals or verified token identity are implied.
Use the event decoder with these full topics and data.