← previous blocknext block →recent activity
Analyzing
Block #106,370,762
13 transactions · 13 stateful · 2026-09-20 04:43:02 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,370,762 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a0016b5…4c4f
0xa6afd3…d132
4 touches
1 conflict
0x7cbbdd3f…65b0
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5ef326ed…69dc
0xa6afd3…d132
4 touches
1 conflict
0x80c5e6ff…9479
0x37db7f…ec7b
2 touches
0 conflicts
0x89789d4d…63f8
0x34b655…2a6f
2 touches
0 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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x9a0016b50f…264c4f
Audit this contract →
← previous block·next block →recent activity