← previous blocknext block →recent activity
Analyzing
Block #103,211,559
18 transactions · 17 stateful · 2026-09-09 02:56:21 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,211,559 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w011w012w113w215w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d28bce…c32c
0x34b655…2a6f
6 touches
3 conflicts
0x0f763490…ff64
0x34b655…2a6f
6 touches
3 conflicts
0x1513b999…b52e
0x34b655…2a6f
6 touches
3 conflicts
0x2d0e3443…7138
0x34b655…2a6f
6 touches
3 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
6 touches
3 conflicts
0xf397d89f…f80e
0x34b655…2a6f
6 touches
3 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
6 touches
3 conflicts
0x6dc1811e…2588
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: Perpl
3 conflicts on slot 0xf5d28bce28…fbc32c
Audit this contract →
← previous block·next block →recent activity