← previous blocknext block →recent activity
Analyzing
Block #106,951,520
24 transactions · 22 stateful · 2026-09-22 05:27:03 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,951,520 · 24 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
1w02w13w24w36w08w09w113w115w217w218w321w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cf31166…d0be
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x34a5dca8…326a
0x34b655…2a6f
6 touches
3 conflicts
0x61531119…de46
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x45b67460…28aa
0x1b6862…e19c
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 0x2cf31166d9…13d0be
Audit this contract →
← previous block·next block →recent activity