← previous blocknext block →recent activity
Analyzing
Block #108,103,656
22 transactions · 22 stateful · 2026-09-26 06:08:33 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,103,656 · 22 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
2w05w06w110w111w214w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf08bda82…71d6
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
6 touches
3 conflicts
0x775a8ad3…8307
0x34b655…2a6f
6 touches
3 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
6 touches
3 conflicts
0x84fe76b9…bd24
0x37db7f…ec7b
6 touches
3 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
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 0xf08bda8277…c171d6
Audit this contract →
← previous block·next block →recent activity