← previous blocknext block →recent activity
Analyzing
Block #108,396,587
10 transactions · 8 stateful · 2026-09-27 06:42:45 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,396,587 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69bb4e1…f2bb
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
5 touches
3 conflicts
0x18289c1e…7766
0x34b655…2a6f
5 touches
3 conflicts
0x942b3403…1f40
0x34b655…2a6f
5 touches
3 conflicts
0x1a73a19b…1ea2
0x34b655…2a6f
5 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 0xa69bb4e112…87f2bb
Audit this contract →
← previous block·next block →recent activity