← previous blocknext block →recent activity
Analyzing
Block #108,336,067
21 transactions · 20 stateful · 2026-09-27 01:38:12 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,336,067 · 21 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
1w02w13w26w08w310w011w112w213w114w315w416w517w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x939cdd56…00c8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x98067f20…59e4
0x1b6862…e19c
8 touches
6 conflicts
0xc32da57a…e33f
0xd32edf…ff58
7 touches
6 conflicts
0x0df117a1…5fc4
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
6 conflicts on slot 0x939cdd567e…a300c8
Audit this contract →
← previous block·next block →recent activity