← previous blocknext block →recent activity
Analyzing
Block #108,676,414
27 transactions · 21 stateful · 2026-09-28 06:11:42 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,676,414 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w111w212w316w217w218w320w021w122w023w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bed9cb…9c43
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc550cc48…815d
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xb8dc136f…fb16
0xc8689a…ee79
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 0x00bed9cbcd…c79c43
Audit this contract →
← previous block·next block →recent activity