← previous blocknext block →recent activity
Analyzing
Block #85,123,733
14 transactions · 12 stateful · 2026-07-02 13:46:15 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,123,733 · 14 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
1w02w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x38b0dd4b…5653
0x065c9d…c394
2 touches
0 conflicts
0x5bde81b3…e21b
0x065c9d…c394
2 touches
0 conflicts
0x9c3c29e8…3ff2
0x065c9d…c394
2 touches
0 conflicts
0xd3dd0704…9957
0x065c9d…c394
2 touches
0 conflicts
0xfd81fa80…fe5e
0x065c9d…c394
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity