← previous blocknext block →recent activity
Analyzing
Block #85,188,032
13 transactions · 12 stateful · 2026-07-02 20:54:45 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,188,032 · 13 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
8w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd1b7caa…e5c5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbb7c40e1…e767
0x065c9d…c394
4 touches
1 conflict
0x0cdf8cbd…ce4c
0x065c9d…c394
3 touches
1 conflict
0xd6dee477…cdb7
0x065c9d…c394
3 touches
1 conflict
0x95c578d5…b856
0x065c9d…c394
3 touches
1 conflict
0x3f64b015…b4d5
0x065c9d…c394
3 touches
1 conflict
0xac2a0273…7212
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 0xfd1b7caaf7…f8e5c5
Audit this contract →
← previous block·next block →recent activity