← previous blocknext block →recent activity
Analyzing
Block #106,109,206
17 transactions · 17 stateful · 2026-09-19 06:46:38 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,109,206 · 17 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
1w02w13w14w27w09w010w111w212w313w414w515w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0105ed2d…077a
0x6f6493…b480
12 touches
15 conflicts
0x0bc0a5b0…decd
0x6f6493…b480
12 touches
15 conflicts
0x0eec8380…5d94
0x6f6493…b480
12 touches
15 conflicts
0x10216f4a…f287
0x6f6493…b480
12 touches
15 conflicts
0x1dee839a…1304
0x6f6493…b480
12 touches
15 conflicts
0x23e4a83a…600b
0x6f6493…b480
12 touches
15 conflicts
0x27a65aba…fa93
0x6f6493…b480
12 touches
15 conflicts
0x29d07190…81fd
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 0x0105ed2d23…53077a
Audit this contract →
← previous block·next block →recent activity