← previous blocknext block →recent activity
Analyzing
Block #106,367,113
33 transactions · 31 stateful · 2026-09-20 04:24:40 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
1.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,367,113 · 33 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
1w02w03w04w15w06w07w19w110w214w116w117w220w321w322w424w525w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd2fd64…69d4
0x34b655…2a6f
14 touches
21 conflicts
0x8d664414…3344
0x34b655…2a6f
14 touches
21 conflicts
0x810a3aa2…0227
0x34b655…2a6f
12 touches
15 conflicts
0x465d39d6…9fc0
0x34b655…2a6f
12 touches
15 conflicts
0xdd77da90…6df4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
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 0x0bd2fd6431…9b69d4
Audit this contract →
← previous block·next block →recent activity