← previous blocknext block →recent activity
Analyzing
Block #108,419,537
13 transactions · 10 stateful · 2026-09-27 08:38:16 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,419,537 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc99d7f64…a643
0x34b655…2a6f
4 touches
1 conflict
0x9b419d78…018b
0x34b655…2a6f
4 touches
1 conflict
0xefc465f2…88c5
0x34b655…2a6f
4 touches
1 conflict
0x30cc27ce…bc89
0x34b655…2a6f
4 touches
1 conflict
0xc4629efd…3374
0x34b655…2a6f
4 touches
1 conflict
0x23a95861…b991
0x34b655…2a6f
2 touches
0 conflicts
0x34886fd6…6f1f
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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 0xc99d7f648e…a5a643
Audit this contract →
← previous block·next block →recent activity