← previous blocknext block →recent activity
Analyzing
Block #86,387,796
17 transactions · 14 stateful · 2026-07-08 10:13:59 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,387,796 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w012w213w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcd0d0528…2f21
0x065c9d…c394
3 touches
1 conflict
0xe72fecb4…e78e
0x065c9d…c394
3 touches
1 conflict
0xc2465761…4493
0x065c9d…c394
3 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