← previous blocknext block →recent activity
Analyzing
Block #85,218,916
14 transactions · 13 stateful · 2026-07-03 00:20:27 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,218,916 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x13227fdf…f748
0x065c9d…c394
6 touches
3 conflicts
0xb8ef02f8…2015
0x065c9d…c394
5 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xfd5a3091…9094
0x34b655…2a6f
4 touches
1 conflict
0x90e113f8…c8f9
0xc8689a…ee79
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0xa605468c…1bfc
0x69df8a…6292
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity