← previous blocknext block →recent activity
Analyzing
Block #87,713,816
55 transactions · 35 stateful · 2026-07-14 14:01:34 UTC
Parallelism
69/100
Blocked
71%
Avg conflicts / tx
2.8
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,713,816 · 55 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
4w07w110w011w115w026w027w128w229w330w431w532w633w734w835w936w1045w246w347w448w549w1153w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
14 touches
21 conflicts
0xa558e115…fc88
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
12 touches
15 conflicts
0xf5e8732e…adea
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xfa551be3…a911
0xa6afd3…d132
10 touches
10 conflicts
0xa6389d47…9a28
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity