← previous blocknext block →recent activity
Analyzing
Block #106,109,722
25 transactions · 23 stateful · 2026-09-19 06:49:14 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,109,722 · 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
1w02w13w24w35w47w515w017w018w119w220w321w422w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08f05e63…b51e
0x6f6493…b480
12 touches
15 conflicts
0x1c554157…ce22
0x6f6493…b480
12 touches
15 conflicts
0x267bf451…04e7
0x6f6493…b480
12 touches
15 conflicts
0x35973e09…3958
0x6f6493…b480
12 touches
15 conflicts
0x38432877…366a
0x6f6493…b480
12 touches
15 conflicts
0x43ea1303…f539
0x6f6493…b480
12 touches
15 conflicts
0x4f44dd5c…113d
0x6f6493…b480
12 touches
15 conflicts
0x4f5a9021…b82d
0x6f6493…b480
12 touches
15 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: 0x6f6493e3…08b480
15 conflicts on slot 0x08f05e6354…f7b51e
Audit this contract →
← previous block·next block →recent activity