LegacyThe original transaction format: one flat gasPrice bid, paid as-is — no base-fee/tip split. Predates the EIP-1559 fee market but remains valid. · raw type: 0
Method
strictlySwapAndCallThe 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.
Tx 212 of 283 in blockPosition in block 25493410: txIndex 211 (zero-based) of 283 transactions
Routed through 10 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.#2#6#10
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.#2#6#10
Native ETH was wrappedA `Deposit` log together with native value on the transaction — ETH turned into its wrapped form. `Deposit` alone would not be enough: staking contracts emit it too.derivedFollows from combining facts (for example a deposit log together with native value). Reasonable, but a reading rather than a statement.#0
Gas hotspotsGas each call burned BY ITSELF — its own consumption minus everything it invoked, since the wire reports gas inclusively. The share is of the root call's gas, not of the transaction fee.
11.0%
5.4%
4.2%
Repeated callsThe same executing code called with the same 4-byte selector more than once. On an arbitrage this is the shape of the strategy itself — no semantic layer needed to see it.
ParticipantsDistinct addresses called, how many calls each took, and how many frames ran someone else's code in their caller's storage (DELEGATECALL/CALLCODE).
FailuresCalls that did not succeed, and where the first one is. Inner failures under a successful root are HANDLED — a try/catch, a probe, a fallback path — which reads very differently from a failed transaction.
2 failedhandled
depthFold the tree to a level: everything deeper than the number you pick is hidden, and the calls AT that level stay visible. Opening one of them then reveals exactly one more level.Show levels 1–1, fold everything belowShow levels 1–2, fold everything belowShow levels 1–3, fold everything belowShow levels 1–4, fold everything belowShow levels 1–5, fold everything belowShow levels 1–6, fold everything belowShow levels 1–7, fold everything belowShow levels 1–8, fold everything below161 calls · depth 9Calls in this trace, including the top-level one, and the deepest nesting level reached.
CALLsuccessdepth 7Nesting level in the call tree. The root transaction call is depth 1 — there is no depth 0.
SenderEffective msg.sender inside this call. A DELEGATECALL inherits it from its caller instead of becoming the sender itself.0xae05...51aa
StateWhose storage this call reads and writes. A DELEGATECALL keeps its caller’s storage — that is what makes a proxy a proxy. Derived from the tree; the wire has no field for it yet.Uniswap V4: PoolManager
CodeContract whose bytecode actually runs. On a DELEGATECALL this differs from the callee, which is only the storage context.Uniswap V4: PoolManager
gas usedGas consumed by this call INCLUDING everything it invoked — measured on this transaction: the root's 931,860 covers its children's 897,251.50,447
gas limitGas made available to this call by its caller — a ceiling, not a charge.1,753,719
selectorThe 4-byte method selector this call was dispatched with.0xf3cd914c