← previous blocknext block →recent activity
Analyzing
Block #108,540,002
20 transactions · 19 stateful · 2026-09-27 18:44:39 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,540,002 · 20 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
1w02w06w08w19w210w211w312w413w516w317w519w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x7d499bce…b0ea
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf06fce24…887d
0x34b655…2a6f
8 touches
6 conflicts
0x260229da…080d
0x34b655…2a6f
6 touches
3 conflicts
0xbdd16b79…7beb
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity