← previous blocknext block →recent activity
Analyzing
Block #106,199,527
24 transactions · 21 stateful · 2026-09-19 14:21:12 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,527 · 24 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
4w05w16w27w313w414w517w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x98568c43…ff4e
0x34b655…2a6f
6 touches
3 conflicts
0x4cff6b80…47a8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd5dc7333…faff
0x34b655…2a6f
6 touches
3 conflicts
0xada087b9…4aca
0x34b655…2a6f
6 touches
3 conflicts
0x656c2ba5…d35b
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity