← previous blocknext block →recent activity
Analyzing
Block #108,587,609
28 transactions · 25 stateful · 2026-09-27 22:44:30 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,587,609 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w08w112w113w115w216w317w418w520w722w123w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bd71786…2d83
0x34b655…2a6f
14 touches
21 conflicts
0xaa427518…d014
0x34b655…2a6f
10 touches
10 conflicts
0xc53799eb…d928
0x34b655…2a6f
8 touches
6 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc7047f2b…36c4
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x5e5fb21b…6960
0x34b655…2a6f
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
21 conflicts on slot 0x2bd7178683…a02d83
Audit this contract →
← previous block·next block →recent activity