← previous blocknext block →recent activity
Analyzing
Block #85,177,010
18 transactions · 18 stateful · 2026-07-02 19:41:21 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,177,010 · 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
1w02w03w17w28w29w310w012w114w116w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0xe1791476…927a
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x276f1d01…5d58
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
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-WETH/USDC
1 conflict on slot 0x987aeb55c2…370e2a
Audit this contract →
← previous block·next block →recent activity