← previous blocknext block →recent activity
Analyzing
Block #85,128,852
31 transactions · 24 stateful · 2026-07-02 14:20:28 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,128,852 · 31 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
1w02w03w14w25w16w07w09w111w216w017w118w219w320w428w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5e4f5326…e322
0x065c9d…c394
5 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity