← previous blocknext block →recent activity
Analyzing
Block #85,126,428
50 transactions · 34 stateful · 2026-07-02 14:04:17 UTC
Parallelism
80/100
Blocked
62%
Avg conflicts / tx
1.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,126,428 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w513w614w736w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x9db94fb8…6300
0xd32edf…ff58
11 touches
15 conflicts
0x22d3c767…e4d1
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
8 touches
6 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity