← previous blocknext block →recent activity
Analyzing
Block #106,188,374
19 transactions · 19 stateful · 2026-09-19 13:25:04 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,188,374 · 19 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
1w02w13w24w06w07w111w012w113w214w315w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01b80c8b…80be
0x6f6493…b480
8 touches
6 conflicts
0x035e2615…b31c
0x6f6493…b480
8 touches
6 conflicts
0x077a635b…3588
0x6f6493…b480
8 touches
6 conflicts
0x1781e2ac…21b1
0x6f6493…b480
8 touches
6 conflicts
0x1ab3499f…3795
0x6f6493…b480
8 touches
6 conflicts
0x2f829888…f54e
0x6f6493…b480
8 touches
6 conflicts
0x34d3afd8…621b
0x6f6493…b480
8 touches
6 conflicts
0x3dbc13a5…f971
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 0x01b80c8b87…6b80be
Audit this contract →
← previous block·next block →recent activity