← previous blocknext block →recent activity
Analyzing
Block #86,385,607
30 transactions · 19 stateful · 2026-07-08 09:59:21 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,385,607 · 30 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
2w04w15w216w017w121w023w324w425w126w227w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xed1360a7…c92c
0xd32edf…ff58
5 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x337e486d…2e79
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity