← previous blocknext block →recent activity
Analyzing
Block #85,927,303
15 transactions · 9 stateful · 2026-07-06 06:59:13 UTC
Parallelism
87/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,927,303 · 15 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f4bf8e0…bddc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7998ccac…e631
0x065c9d…c394
3 touches
1 conflict
0x1581a86c…aa4c
0x065c9d…c394
3 touches
1 conflict
0x0e081eda…80fa
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x28705a92…59ae
0x065c9d…c394
2 touches
0 conflicts
0x489fafcb…9780
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 0x3f4bf8e014…e4bddc
Audit this contract →
← previous block·next block →recent activity