← previous blocknext block →recent activity
Analyzing
Block #85,169,991
39 transactions · 33 stateful · 2026-07-02 18:54:38 UTC
Parallelism
72/100
Blocked
73%
Avg conflicts / tx
2.62
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #85,169,991 · 39 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w410w512w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad3280d…16bb
0x34b655…2a6f
16 touches
28 conflicts
0x47ad0873…70d5
0xd32edf…ff58
15 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002a
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xfac61869…a55d
0x1b6862…e19c
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
28 conflicts on slot 0x5ad3280dca…f116bb
Audit this contract →
← previous block·next block →recent activity