← previous blocknext block →recent activity
Analyzing
Block #87,700,388
71 transactions · 59 stateful · 2026-07-14 12:31:31 UTC
Parallelism
76/100
Blocked
75%
Avg conflicts / tx
2.59
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,700,388 · 71 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w27w313w215w316w418w519w620w721w324w125w426w527w628w756w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x16f92e21…621c
0xd32edf…ff58
15 touches
28 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x900900c7…0a3e
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity