← previous blocknext block →recent activity
Analyzing
Block #106,415,004
19 transactions · 18 stateful · 2026-09-20 08:25:41 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,415,004 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w29w310w411w513w314w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x799f4636…f628
0x34b655…2a6f
10 touches
10 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x4265984a…a7d2
0x34b655…2a6f
6 touches
3 conflicts
0x46193937…38a7
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x998a1167…81f9
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 0x799f4636c0…6af628
Audit this contract →
← previous block·next block →recent activity