← previous blocknext block →recent activity
Analyzing
Block #85,172,710
30 transactions · 24 stateful · 2026-07-02 19:12:40 UTC
Parallelism
80/100
Blocked
54%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,172,710 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w37w318w423w424w525w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x6f26ffcf…6937
0xd32edf…ff58
7 touches
6 conflicts
0xcb216851…a8b5
0x065c9d…c394
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 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: USDC (USDC)
15 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity