← previous blocknext block →recent activity
Analyzing
Block #108,515,365
20 transactions · 20 stateful · 2026-09-27 16:40:39 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,515,365 · 20 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
3w04w19w014w115w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88cf2d31…3d64
0x34b655…2a6f
8 touches
6 conflicts
0xce594bed…4d7c
0x34b655…2a6f
8 touches
6 conflicts
0xd8eeaf66…cb95
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
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 0x88cf2d3101…3b3d64
Audit this contract →
← previous block·next block →recent activity