← previous blocknext block →recent activity
Analyzing
Block #109,177,187
26 transactions · 19 stateful · 2026-09-30 00:19:11 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,177,187 · 26 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
1w03w04w15w07w18w212w016w117w120w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x336486a4…20bd
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x3222dfa2…75c4
0x34b655…2a6f
4 touches
1 conflict
0x7d9ef283…ddd1
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 0x336486a4ab…4220bd
Audit this contract →
← previous block·next block →recent activity