← previous blocknext block →recent activity
Analyzing
Block #85,680,845
15 transactions · 12 stateful · 2026-07-05 03:36:28 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,680,845 · 15 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
1w02w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3b6de764…9a01
0xd32edf…ff58
3 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x6863d5d1…05e7
0x065c9d…c394
2 touches
0 conflicts
0x9247d5ee…5167
0x065c9d…c394
2 touches
0 conflicts
0xa7913482…4541
0x065c9d…c394
2 touches
0 conflicts
0xe72ae6f2…4edf
0x065c9d…c394
2 touches
0 conflicts
0xf6f617ed…482b
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity