← previous blocknext block →recent activity
Analyzing
Block #85,760,697
12 transactions · 8 stateful · 2026-07-05 12:29:32 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,760,697 · 12 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x19d6f4fc…bee2
0x065c9d…c394
2 touches
0 conflicts
0x46171a9d…bf7f
0x065c9d…c394
2 touches
0 conflicts
0x9306b1db…d57c
0x065c9d…c394
2 touches
0 conflicts
0xcb18b621…f34c
0x065c9d…c394
2 touches
0 conflicts
0xd361246a…db8d
0x065c9d…c394
2 touches
0 conflicts
0xec7c6fb5…0653
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity