← previous blocknext block →recent activity
Analyzing
Block #106,950,111
17 transactions · 17 stateful · 2026-09-22 05:19:58 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,950,111 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w08w09w110w111w012w213w315w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37e40b32…c169
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x37e40b32f6…06c169
Audit this contract →
← previous block·next block →recent activity