← previous blocknext block →recent activity
Analyzing
Block #106,923,294
36 transactions · 34 stateful · 2026-09-22 03:04:59 UTC
Parallelism
56/100
Blocked
68%
Avg conflicts / tx
3.36
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,923,294 · 36 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w19w210w311w412w513w114w415w516w617w718w819w920w1021w1128w229w1230w1331w1432w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
24 touches
66 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0x8c572c8c…280b
0x34b655…2a6f
18 touches
36 conflicts
0x53690737…855a
0x34b655…2a6f
16 touches
28 conflicts
0x206f4379…e08a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x69411fb3…e36d
0x34b655…2a6f
12 touches
15 conflicts
0xf5ebddff…341c
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity