← previous blocknext block →recent activity
Analyzing
Block #85,792,023
13 transactions · 11 stateful · 2026-07-05 15:58:08 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,792,023 · 13 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbfcbd642…ae4e
0x065c9d…c394
4 touches
1 conflict
0x527ff584…5c54
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x67ea39d0…ba0a
0x065c9d…c394
3 touches
1 conflict
0x1955f57c…f3a4
0x065c9d…c394
3 touches
1 conflict
0x6dfa1723…4718
0x34b655…2a6f
2 touches
0 conflicts
0x6dfa1723…4719
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity