← previous blocknext block →recent activity
Analyzing
Block #106,958,209
37 transactions · 34 stateful · 2026-09-22 06:00:44 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,958,209 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w08w110w114w115w216w320w221w322w223w324w432w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x5357f8a3…c0af
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x1b3df55c…8693
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x91cd366d…5cea
0x34b655…2a6f
8 touches
6 conflicts
0xe51d2911…32de
0x34b655…2a6f
8 touches
6 conflicts
0xd125c3f8…99aa
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
10 conflicts on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity