← previous blocknext block →recent activity
Analyzing
Block #106,185,405
24 transactions · 22 stateful · 2026-09-19 13:10:08 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.88
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,185,405 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w312w413w514w615w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x854ce402…932a
0x34b655…2a6f
14 touches
21 conflicts
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0xb550abea…2729
0x34b655…2a6f
6 touches
3 conflicts
0xcc844ab5…4c6d
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity