← previous blocknext block →recent activity
Analyzing
Block #106,429,635
24 transactions · 21 stateful · 2026-09-20 09:39:18 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,429,635 · 24 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
1w02w03w14w05w110w115w016w117w218w321w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01335211…c6c9
0x6f6493…b480
8 touches
6 conflicts
0x097589c7…dd4c
0x6f6493…b480
8 touches
6 conflicts
0x1a4e098a…7de5
0x6f6493…b480
8 touches
6 conflicts
0x207d8cd7…b18f
0x6f6493…b480
8 touches
6 conflicts
0x2198321f…2409
0x6f6493…b480
8 touches
6 conflicts
0x26ee323c…654d
0x6f6493…b480
8 touches
6 conflicts
0x34a896c3…6542
0x6f6493…b480
8 touches
6 conflicts
0x372493bc…6e2b
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 0x013352119f…33c6c9
Audit this contract →
← previous block·next block →recent activity