← previous blocknext block →recent activity
Analyzing
Block #85,804,045
20 transactions · 20 stateful · 2026-07-05 17:18:17 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,804,045 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w29w110w211w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46b62326…9b3c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xe95aac8c…4e93
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x89750670…2dea
0xa6afd3…d132
4 touches
1 conflict
0x80f47a73…bffe
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-WETH/USDC
3 conflicts on slot 0x46b62326eb…ce9b3c
Audit this contract →
← previous block·next block →recent activity