← previous blocknext block →recent activity
Analyzing
Block #85,807,220
14 transactions · 8 stateful · 2026-07-05 17:39:28 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,807,220 · 14 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xfc1a1820…6377
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xa3abd9a5…fe78
0x065c9d…c394
4 touches
1 conflict
0x30397a71…45d5
0x065c9d…c394
3 touches
1 conflict
0x81e92a84…1795
0x065c9d…c394
3 touches
1 conflict
0xa0c4c280…2e4b
0x065c9d…c394
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity