← previous blocknext block →recent activity
Analyzing
Block #105,925,140
22 transactions · 21 stateful · 2026-09-18 15:20:07 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,925,140 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w210w312w013w114w116w117w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x533f02b5…b4dc
0x6f6493…b480
8 touches
6 conflicts
0x1c86956f…ae4f
0x6f6493…b480
8 touches
6 conflicts
0x533f02b5…b4d8
0x6f6493…b480
8 touches
6 conflicts
0xa3a9af6b…d1b0
0x6f6493…b480
8 touches
6 conflicts
0xc0e83411…dad8
0x6f6493…b480
8 touches
6 conflicts
0xc9a051fc…6786
0x6f6493…b480
8 touches
6 conflicts
0xcacd41fc…5835
0x6f6493…b480
8 touches
6 conflicts
0xe1dfd5cc…0a84
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: 0x6f6493e3…08b480
6 conflicts on slot 0x533f02b5d1…beb4dc
Audit this contract →
← previous block·next block →recent activity