← previous blocknext block →recent activity
Analyzing
Block #85,920,062
36 transactions · 30 stateful · 2026-07-06 06:11:00 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,920,062 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w29w210w011w112w218w019w022w323w424w125w526w133w234w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x160f117d…8e90
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 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-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity