← previous blocknext block →recent activity

Analyzing

Block #112,482,680

27 transactions · 23 stateful · 2026-10-11 13:39:07 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #112,482,680  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xbc222c2e…2229

0xd32edf…ff58

9 touches
10 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0xa4fd1b6f…d735

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xccebf5c5…8758

0x34b655…2a6f

6 touches
3 conflicts

0xbc1f23d0…962e

0x34b655…2a6f

6 touches
3 conflicts

0x931975c2…b7b3

0x34b655…2a6f

6 touches
3 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: FastLane: FastLaneAuctionHandler

10 conflicts on slot 0xbc222c2e39…ce2229

← previous block·next block →recent activity