← previous blocknext block →recent activity
Analyzing
Block #85,131,201
67 transactions · 51 stateful · 2026-07-02 14:36:12 UTC
Parallelism
72/100
Blocked
71%
Avg conflicts / tx
2.84
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #85,131,201 · 67 txs across 19 waves · depth 19
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w07w311w112w213w314w419w020w124w125w026w127w246w547w648w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xb04d17a0…10e8
0x34b655…2a6f
12 touches
15 conflicts
0xa678cd56…4fab
0x34b655…2a6f
12 touches
15 conflicts
0x79fade94…7f93
0x34b655…2a6f
10 touches
10 conflicts
0xa9988419…9f45
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: Perpl
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity