← previous blocknext block →recent activity
Analyzing
Block #106,424,728
14 transactions · 14 stateful · 2026-09-20 09:14:37 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,424,728 · 14 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
3w04w06w18w29w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe63b3705…28bc
0x34b655…2a6f
8 touches
6 conflicts
0xb5d1cad9…40b0
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0x6b45276b…7636
0x40c49f…2af0
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0xe63b3705df…7328bc
Audit this contract →
← previous block·next block →recent activity