← previous blocknext block →recent activity
Analyzing
Block #106,383,630
23 transactions · 21 stateful · 2026-09-20 05:47:48 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
2.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,383,630 · 23 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
1w02w15w28w09w310w113w414w515w516w617w718w820w622w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9660f3bd…17ce
0x34b655…2a6f
18 touches
36 conflicts
0xb9b077a8…e029
0x34b655…2a6f
12 touches
15 conflicts
0xba33378a…f1df
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
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
36 conflicts on slot 0x9660f3bd9e…8b17ce
Audit this contract →
← previous block·next block →recent activity