← previous blocknext block →recent activity
Analyzing
Block #104,192,588
22 transactions · 19 stateful · 2026-09-12 13:33:43 UTC
Parallelism
73/100
Blocked
37%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,192,588 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w212w213w314w419w020w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91f679af…6ac5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x27034002…2f27
0x34b655…2a6f
6 touches
3 conflicts
0x483c2974…bee4
0x34b655…2a6f
6 touches
3 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
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
10 conflicts on slot 0x91f679af07…936ac5
Audit this contract →
← previous block·next block →recent activity