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
transferAndMulticallThe 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 28 of 303 in blockPosition in block 25790084: txIndex 27 (zero-based) of 303 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.#10#12#22
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.#10#12#22
A spending allowance was setAn `Approval` log: an allowance was set, letting a spender move tokens later. Nothing moved in this transaction because of it.confirmedRead from a standard event or a structural fact of the call tree — the transaction says this outright.#2#4
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.
9.3%
8.0%
5.0%
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.
1 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 below279 calls · depth 12Calls in this trace, including the top-level one, and the deepest nesting level reached.
CALLsuccessdepth 1Nesting 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.0x4e10...7f79
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.RelayApprovalProxyV3
CodeContract whose bytecode actually runs. On a DELEGATECALL this differs from the callee, which is only the storage context.RelayApprovalProxyV3
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.2,453,649
gas limitGas made available to this call by its caller — a ceiling, not a charge.2,496,331
selectorThe 4-byte method selector this call was dispatched with.transferAndMulticalltransferAndMulticall0xf9e4bab4