← previous blocknext block →recent activity
Analyzing
Block #106,932,853
24 transactions · 22 stateful · 2026-09-22 03:53:05 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,853 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w011w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 conflicts
0x643113d0…43d7
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x9eef1610…1564
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xf75d2778…4de5
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
21 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity