← previous blocknext block →recent activity
Analyzing
Block #106,207,725
25 transactions · 23 stateful · 2026-09-19 15:02:31 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,207,725 · 25 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
1w03w04w07w19w110w211w216w317w018w419w521w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb808cfd…e52a
0x34b655…2a6f
10 touches
10 conflicts
0xaef82336…d052
0x34b655…2a6f
8 touches
6 conflicts
0xff4fd690…957d
0x34b655…2a6f
6 touches
3 conflicts
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x879faaf6…d0c8
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 0xbb808cfd89…29e52a
Audit this contract →
← previous block·next block →recent activity