← previous blocknext block →recent activity
Analyzing
Block #87,716,063
52 transactions · 45 stateful · 2026-07-14 14:16:41 UTC
Parallelism
65/100
Blocked
69%
Avg conflicts / tx
3.13
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,716,063 · 52 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w110w011w112w221w522w634w737w138w339w841w242w344w1445w1046w1547w1648w449w551w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0x8b818135…eff8
0x34b655…2a6f
14 touches
21 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
12 touches
15 conflicts
0x747f609d…1555
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x92385428…6941
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