← previous blocknext block →recent activity
Analyzing
Block #85,797,518
23 transactions · 17 stateful · 2026-07-05 16:34:45 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,797,518 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w18w09w411w115w516w620w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc835f5f0…c21e
0xd32edf…ff58
7 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x1243f6ba…6fbf
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x4bc3aee7…9aec
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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