← previous blocknext block →recent activity
Analyzing
Block #106,930,873
20 transactions · 19 stateful · 2026-09-22 03:43:08 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,930,873 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w19w110w211w312w414w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1556ed58…0d33
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
8 touches
6 conflicts
0xf782ee27…41cd
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x85c5ea16…1194
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 0x1556ed5826…150d33
Audit this contract →
← previous block·next block →recent activity