← previous blocknext block →recent activity
Analyzing
Block #86,960,362
21 transactions · 19 stateful · 2026-07-11 02:02:46 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,960,362 · 21 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
1w03w05w06w18w19w011w213w114w315w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0xa112f315…1a92
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0x1f396cee…862f
0x34b655…2a6f
4 touches
1 conflict
0x208b7ea0…b57f
0x34b655…2a6f
4 touches
1 conflict
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity