← previous blocknext block →recent activity
Analyzing
Block #106,801,274
24 transactions · 23 stateful · 2026-09-21 16:50:48 UTC
Parallelism
54/100
Blocked
57%
Avg conflicts / tx
1.92
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,801,274 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w211w312w413w514w615w116w517w718w819w920w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e6832ca…0340
0x34b655…2a6f
16 touches
28 conflicts
0x371b8d95…d138
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8a02d049…f481
0x34b655…2a6f
8 touches
6 conflicts
0x9ba5adab…cacc
0x34b655…2a6f
8 touches
6 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0xdcd83028…833c
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
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
28 conflicts on slot 0x1e6832ca35…920340
Audit this contract →
← previous block·next block →recent activity