EIP-1559Dynamic-fee transaction: the sender caps the total price (maxFeePerGas) and tips the validator (maxPriorityFeePerGas); the network burns the base fee and refunds the unused headroom (EIP-1559). · raw type: 2
Method
bhijdgacekfThe function this transaction called, by its 4-byte selector. A bare 0x… selector is not in our signature set — not a call that did nothing.
All Tokens5Every token this transaction movedWrapped Ether30xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2Aave Token10x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9Pepe (PEPE)10x6982508145454ce325ddbe47a25d4ec3d2311933
1 of 5
Signed by0x0000...089b0x00000000fd3a7b3fa5bcfa843c648714b11e089bcalling0x0000...089b0x00000000fd3a7b3fa5bcfa843c648714b11e089b
Tx 163 of 256 in blockPosition in block 25401575: txIndex 162 (zero-based) of 256 transactions
The sender ended up ahead in one token after a round tripTwo or more swaps after which the sender is up in exactly one token and square in every other. A plain multi-hop leaves them down one token, so this pattern is what distinguishes profit from a route.derivedFollows from combining facts (for example a deposit log together with native value). Reasonable, but a reading rather than a statement.#3#4#5
Routed through 4 poolsSeveral swaps where a token one leg received is the token the next leg sends — a route through pools rather than independent trades.derivedFollows from combining facts (for example a deposit log together with native value). Reasonable, but a reading rather than a statement.#3#4#5
Tokens were swappedA `Swap` log, the standard pool event. The evidence links show how many logs there were — the count is deliberately not stated as a number of swaps, because a router re-emits the pool’s event under its own address.confirmedRead from a standard event or a structural fact of the call tree — the transaction says this outright.#3#4#5
Net flowwhat each address ended up with, derived from the transfers below