← previous blocknext block →recent activity
Analyzing
Block #85,916,757
37 transactions · 31 stateful · 2026-07-06 05:48:59 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,916,757 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w09w110w211w312w013w117w018w121w125w026w434w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0x119e6da3…9773
0xd32edf…ff58
5 touches
3 conflicts
0x6107c5c9…f9db
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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 0xb33ff82315…a81188
Audit this contract →
← previous block·next block →recent activity