← previous blocknext block →recent activity
Analyzing
Block #106,042,051
24 transactions · 21 stateful · 2026-09-19 01:08:41 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,042,051 · 24 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
1w02w13w24w210w215w016w117w218w321w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x00648793…47ab
0x6f6493…b480
8 touches
6 conflicts
0x0b4cd186…c61a
0x6f6493…b480
8 touches
6 conflicts
0x124fdeb1…a2dc
0x6f6493…b480
8 touches
6 conflicts
0x15cd82d6…8883
0x6f6493…b480
8 touches
6 conflicts
0x19b21533…ada1
0x6f6493…b480
8 touches
6 conflicts
0x1deef058…4648
0x6f6493…b480
8 touches
6 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
6 conflicts on slot 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity