← previous blocknext block →recent activity
Analyzing
Block #106,016,242
13 transactions · 12 stateful · 2026-09-18 22:58:48 UTC
Parallelism
54/100
Blocked
58%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,016,242 · 13 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
1w02w15w16w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x072fbbd6…1a27
0x6f6493…b480
11 touches
15 conflicts
0x11293375…ed63
0x6f6493…b480
11 touches
15 conflicts
0x16550762…0e1b
0x6f6493…b480
11 touches
15 conflicts
0x1886b1b4…ba3b
0x6f6493…b480
11 touches
15 conflicts
0x204c5fe5…83e0
0x6f6493…b480
11 touches
15 conflicts
0x255f593b…27c1
0x6f6493…b480
11 touches
15 conflicts
0x2b961a87…c45f
0x6f6493…b480
11 touches
15 conflicts
0x324888e0…50ca
0x6f6493…b480
11 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 0x072fbbd6cb…741a27
Audit this contract →
← previous block·next block →recent activity