Analyses: Same Wallet, Same Contract, Different Chain Architecture
Comparative execution and confirmation behavior across Ethereum and Polkadot Hub mainnets.
Polkadot Hub
chainId: 420420419
Contract:
0x1f55aDbFc8c2A5DF67498563fBE5B455E5e0d168Status: idle
Confirm time
-
Block #
-
gasUsed
-
effectiveGasPrice (wei)
-
fee (wei)
-
fee (18dp display)
-
Ethereum Mainnet
chainId: 1
Contract:
0x1f55aDbFc8c2A5DF67498563fBE5B455E5e0d168Status: idle
Confirm time
-
Block #
-
gasUsed
-
effectiveGasPrice (wei)
-
fee (wei)
-
fee (18dp display)
-
Methodology
- Same connected wallet is used for both lanes.
- Same `race(nonce)` contract call is executed on both networks.
- Primary metric is user-observed latency: send to first receipt.
- Comparison is analytical, not protocol-finality equivalence.