← previous blocknext block →recent activity
Analyzing
Block #85,568,878
71 transactions · 61 stateful · 2026-07-04 15:11:00 UTC
Parallelism
69/100
Blocked
80%
Avg conflicts / tx
3.32
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #85,568,878 · 71 txs across 22 waves · depth 22
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w06w17w211w212w313w014w117w218w344w348w150w451w552w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
14 touches
21 conflicts
0x56153262…21ce
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
12 touches
15 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
10 touches
10 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: 0x04fdeac2…f747d7
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity