← previous blocknext block →recent activity
Analyzing
Block #108,515,883
33 transactions · 30 stateful · 2026-09-27 16:43:16 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,515,883 · 33 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
2w06w07w19w111w214w316w017w119w320w423w526w132w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fa4ba1b…750c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0xa535179d…f9dc
0x34b655…2a6f
6 touches
3 conflicts
0x189fbafb…47ca
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x8fa4ba1b4e…e5750c
Audit this contract →
← previous block·next block →recent activity