← previous blocknext block →recent activity
Analyzing
Block #106,216,138
22 transactions · 21 stateful · 2026-09-19 15:44:51 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,216,138 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w012w113w214w316w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe791686c…a1d1
0x34b655…2a6f
12 touches
15 conflicts
0x17d5b5a7…631b
0x34b655…2a6f
6 touches
3 conflicts
0x638cd0f2…cb93
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e2ea201…12de
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
15 conflicts on slot 0xe791686cd7…92a1d1
Audit this contract →
← previous block·next block →recent activity