← previous blocknext block →recent activity
Analyzing
Block #85,195,402
11 transactions · 10 stateful · 2026-07-02 21:43:52 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,195,402 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fbf3c26…9931
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc8c39eb0…38c9
0x754704…b603
4 touches
1 conflict
0xf76fd3e7…53cc
0x754704…b603
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x49a3289a…3797
0x34b655…2a6f
2 touches
0 conflicts
0x8b1b058b…0435
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-MON/USDC
1 conflict on slot 0x6fbf3c26f5…d39931
Audit this contract →
← previous block·next block →recent activity