← previous blocknext block →recent activity
Analyzing
Block #106,386,159
18 transactions · 16 stateful · 2026-09-20 06:00:31 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,386,159 · 18 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
1w02w13w210w011w112w213w314w415w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x063ce12d…c377
0x6f6493…b480
12 touches
15 conflicts
0x06d2fbfc…7b4f
0x6f6493…b480
12 touches
15 conflicts
0x0a22edb7…50f2
0x6f6493…b480
12 touches
15 conflicts
0x0eee1a29…cf7b
0x6f6493…b480
12 touches
15 conflicts
0x0eee1a29…cf7f
0x6f6493…b480
12 touches
15 conflicts
0x0f4c85e5…2e6a
0x6f6493…b480
12 touches
15 conflicts
0x245e3754…9a95
0x6f6493…b480
12 touches
15 conflicts
0x39207d75…3103
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 0x063ce12da8…fac377
Audit this contract →
← previous block·next block →recent activity