← previous blocknext block →recent activity
Analyzing
Block #85,897,426
16 transactions · 13 stateful · 2026-07-06 03:40:13 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,897,426 · 16 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
1w04w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0x11e143e6…d9e1
0x065c9d…c394
2 touches
0 conflicts
0x4f4c2ebe…c842
0x065c9d…c394
2 touches
0 conflicts
0x89b1d2f5…97fa
0x065c9d…c394
2 touches
0 conflicts
0x8df77109…d504
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
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 0xd35bb5ac3f…003586
Audit this contract →
← previous block·next block →recent activity