← previous blocknext block →recent activity
Analyzing
Block #106,328,239
20 transactions · 18 stateful · 2026-09-20 01:09:02 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,328,239 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w09w110w211w312w415w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015e39ac…58d8
0x6f6493…b480
10 touches
10 conflicts
0x108ea7b9…e2b3
0x6f6493…b480
10 touches
10 conflicts
0x15933217…e547
0x6f6493…b480
10 touches
10 conflicts
0x1f7d5f03…e42e
0x6f6493…b480
10 touches
10 conflicts
0x2b0bf990…c619
0x6f6493…b480
10 touches
10 conflicts
0x2b0bf990…c61d
0x6f6493…b480
10 touches
10 conflicts
0x2b3082b6…daf4
0x6f6493…b480
10 touches
10 conflicts
0x38fcee2c…328c
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x015e39ac72…6558d8
Audit this contract →
← previous block·next block →recent activity