← previous blocknext block →recent activity
Analyzing
Block #85,195,357
18 transactions · 18 stateful · 2026-07-02 21:43:34 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,195,357 · 18 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
1w02w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x15b249e6…11d5
0x065c9d…c394
2 touches
0 conflicts
0x3d796fac…96d7
0x065c9d…c394
2 touches
0 conflicts
0x660fbdb2…2a99
0x065c9d…c394
2 touches
0 conflicts
0x8536e54f…ee28
0x065c9d…c394
2 touches
0 conflicts
0x973a5394…14ab
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity