← previous blocknext block →recent activity
Analyzing
Block #106,235,506
19 transactions · 18 stateful · 2026-09-19 17:22:23 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,506 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w38w29w110w111w412w513w517w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e5e1b51…642d
0x34b655…2a6f
10 touches
10 conflicts
0x346d356f…819d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x76bb94df…daf6
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
10 conflicts on slot 0x5e5e1b51b9…83642d
Audit this contract →
← previous block·next block →recent activity