← previous blocknext block →recent activity
Analyzing
Block #85,506,339
10 transactions · 9 stateful · 2026-07-04 08:14:40 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,506,339 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde4ecf7a…26ad
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3cbaadd7…0d70
0x065c9d…c394
3 touches
1 conflict
0xf968f424…a419
0x065c9d…c394
3 touches
1 conflict
0x71ca72eb…45d1
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x79ba20f5…286c
0x065c9d…c394
2 touches
0 conflicts
0xe7da2915…73ba
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 0xde4ecf7a48…a426ad
Audit this contract →
← previous block·next block →recent activity