← previous blocknext block →recent activity
Analyzing
Block #108,796,636
21 transactions · 19 stateful · 2026-09-28 16:17:20 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,796,636 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w210w313w115w420w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
8 touches
6 conflicts
0x715645a4…2cbd
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xddca2daa…b08e
0x34b655…2a6f
6 touches
3 conflicts
0xe2d50773…c39e
0x34b655…2a6f
6 touches
3 conflicts
0x238d0a65…428b
0x37db7f…ec7b
6 touches
3 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
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
6 conflicts on slot 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity