← previous blocknext block →recent activity
Analyzing
Block #106,382,286
15 transactions · 14 stateful · 2026-09-20 05:41:02 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,382,286 · 15 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
1w02w13w04w16w07w08w19w210w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x036b1d3e…6f29
0x6f6493…b480
8 touches
6 conflicts
0x044e2158…df84
0x6f6493…b480
8 touches
6 conflicts
0x0c318422…27ea
0x6f6493…b480
8 touches
6 conflicts
0x0e528fe7…39f2
0x6f6493…b480
8 touches
6 conflicts
0x1d1de14c…47b2
0x6f6493…b480
8 touches
6 conflicts
0x280e6a72…7c41
0x6f6493…b480
8 touches
6 conflicts
0x2a39d9e1…7e1d
0x6f6493…b480
8 touches
6 conflicts
0x2f6a2cdd…2ca0
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 0x036b1d3e54…f96f29
Audit this contract →
← previous block·next block →recent activity