← previous blocknext block →recent activity
Analyzing
Block #108,500,924
25 transactions · 21 stateful · 2026-09-27 15:27:57 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,500,924 · 25 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
1w02w04w16w07w18w213w314w417w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3df7e06d…cd75
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x51255a02…8a05
0x34b655…2a6f
4 touches
1 conflict
0x6674a6df…0368
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity