← previous blocknext block →recent activity
Analyzing
Block #85,515,822
8 transactions · 8 stateful · 2026-07-04 09:17:44 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,515,822 · 8 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4679a7de…54f9
0x065c9d…c394
4 touches
1 conflict
0x0b3a72d1…718e
0x065c9d…c394
4 touches
1 conflict
0x748a1433…5935
0x065c9d…c394
3 touches
1 conflict
0x87a3d818…b3e1
0x065c9d…c394
3 touches
1 conflict
0xbd8459a0…b6e8
0x065c9d…c394
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity