← previous blocknext block →recent activity
Analyzing
Block #85,568,817
58 transactions · 50 stateful · 2026-07-04 15:10:36 UTC
Parallelism
66/100
Blocked
72%
Avg conflicts / tx
3.26
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #85,568,817 · 58 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w212w313w416w518w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xb0446875…2b96
0x34b655…2a6f
16 touches
28 conflicts
0x92c1cdc7…f4ae
0xd32edf…ff58
15 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x31616f97…1acc
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 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: Perpl
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity