← previous blocknext block →recent activity
Analyzing
Block #106,951,136
20 transactions · 19 stateful · 2026-09-22 05:25:07 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
1.65
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,951,136 · 20 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
2w03w14w05w27w08w19w310w211w412w215w516w617w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc953c572…34b1
0x34b655…2a6f
12 touches
15 conflicts
0xcc6a939b…c543
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xc4c059d8…185d
0x34b655…2a6f
8 touches
6 conflicts
0x6aa5d746…f5c1
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x1089878b…0c6f
0xd32edf…ff58
5 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
15 conflicts on slot 0xc953c57268…e534b1
Audit this contract →
← previous block·next block →recent activity