← previous blocknext block →recent activity
Analyzing
Block #108,568,314
18 transactions · 17 stateful · 2026-09-27 21:07:22 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,568,314 · 18 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
2w04w19w110w211w312w413w517w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19dcf812…44d9
0x34b655…2a6f
10 touches
10 conflicts
0x8040cfde…17ca
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe77c721b…7588
0x34b655…2a6f
6 touches
3 conflicts
0xf7213a75…8d13
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
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
10 conflicts on slot 0x19dcf812b9…df44d9
Audit this contract →
← previous block·next block →recent activity