← previous blocknext block →recent activity
Analyzing
Block #85,632,196
22 transactions · 11 stateful · 2026-07-04 22:12:36 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,632,196 · 22 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
1w03w04w15w27w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4e906871…b7e7
0x065c9d…c394
4 touches
2 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x722f5f69…a1eb
0x065c9d…c394
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
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-MON/USDC
3 conflicts on slot 0x5540f95607…2d69e8
Audit this contract →
← previous block·next block →recent activity