← previous blocknext block →recent activity
Analyzing
Block #87,707,682
68 transactions · 52 stateful · 2026-07-14 13:20:30 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
3.01
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,707,682 · 68 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
4w05w17w28w310w411w519w627w028w129w230w332w451w559w760w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x2385516f…eca5
0x34b655…2a6f
10 touches
10 conflicts
0x58aa2cb3…5758
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
120 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity