How would Glamsterdam change this transaction's gas?

Paste the hash of any Ethereum mainnet transaction. Gasworks reprices its original trace under the pinned Glamsterdam Devnet 8 gas rules. The estimate assumes the transaction follows its original execution path.

Try an example

Simple ETH transfer0x59a8d817…3f55e3 · ±0 gas Small contract call0x2823d66c…962e9a · +720 gas Storage-heavy call, tight limit0x060414d9…bc878e · replay required Complex contract interaction0x2f639ed0…612acf · replay required

How it works

Gasworks fetches the transaction, its receipt and the debug_traceTransaction traces from a hosted archive node — it never runs an EVM itself.
The normalized trace is repriced under the immutable ruleset glamsterdam-devnet-8-v8.1.0-eels-864fa03a-r1, covering calldata floors, state creation gas and access repricing.
When the new rules could change the execution path (possible out-of-gas, gasleft() branches, new opcode semantics), Gasworks reports replay required instead of presenting a gas total under the signed limit. When the original trace is complete, it may also retry the observed path with a higher gas limit and show a clearly labeled conditional estimate; this is not a full replay.

Glamsterdam is a draft protocol. Estimates reflect the current Devnet 8 rules, not final gas costs. See the methodology for assumptions and limits.