← previous blocknext block →recent activity
Analyzing
Block #108,009,709
11 transactions · 11 stateful · 2026-09-25 22:15:49 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,009,709 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0x7f9d6f63…90bc
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x24cca2db…458a
0x34b655…2a6f
2 touches
0 conflicts
0x42744667…0b8a
0x34b655…2a6f
2 touches
0 conflicts
0x85f66c9b…30b1
0x34b655…2a6f
2 touches
0 conflicts
0xac0ec150…6179
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x9674d68053…c5261b
Audit this contract →
← previous block·next block →recent activity