← previous blocknext block →recent activity
Analyzing
Block #85,189,651
11 transactions · 9 stateful · 2026-07-02 21:05:31 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,189,651 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2ed59088…446f
0x065c9d…c394
2 touches
0 conflicts
0x758515e5…38ec
0x065c9d…c394
2 touches
0 conflicts
0x8c9c28de…dbd4
0x065c9d…c394
2 touches
0 conflicts
0xb07fc03d…a9f8
0x065c9d…c394
2 touches
0 conflicts
0xb0af9b81…2cb5
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity