← previous blocknext block →recent activity
Analyzing
Block #85,919,524
16 transactions · 10 stateful · 2026-07-06 06:07:24 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,919,524 · 16 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
1w06w07w19w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01660ac6…246c
0x065c9d…c394
3 touches
1 conflict
0x5c27822e…966b
0x065c9d…c394
3 touches
1 conflict
0x3e4ac6b2…41ca
0x34b655…2a6f
2 touches
0 conflicts
0x5300ada7…f01e
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
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