← previous blocknext block →recent activity
Analyzing
Block #85,172,409
18 transactions · 16 stateful · 2026-07-02 19:10:39 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,172,409 · 18 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
1w02w13w24w05w16w09w113w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x631bf923…f2b7
0x065c9d…c394
5 touches
3 conflicts
0xd4f492ce…24eb
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0001
0x120151…c1d6
4 touches
1 conflict
0x00000000…0003
0x120151…c1d6
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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
3 conflicts on slot 0x631bf923a3…eef2b7
Audit this contract →
← previous block·next block →recent activity