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
0xa632fd63The 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 Tokens2Every token this transaction movedWrapped BTC10x2260fac5e5542a773aa44fbcfedf7c193bc2c599Wrapped Ether10xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
Signed by0x825c...049e0x825c4ccb9f6b7d8ade080d13d0d37a16bf37049ecallingMEV Bot: 0xba47...e51MEV Bot: 0xba47...e51 (0xba47cbfdd61029833841fcaa2ec2591ddfa87e51)
Tx 5 of 320 in blockPosition in block 25032450: txIndex 4 (zero-based) of 320 transactions
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.#0
Two independent branches — a bundle, or the two sides of one exchangeThe top-level call fanned out into branches that share no counterparties. With three or more that is a bundle; with exactly two it is genuinely undecidable — an exchange also sends goods one way and payment another, and those branches share nothing either.ambiguousSeveral readings fit the same evidence. Shown so it is not silently dropped, not because one of them was picked.↳frame↳frame
Net flowwhat each address ended up with, derived from the transfers below