← previous blocknext block →recent activity
Analyzing
Block #87,714,371
57 transactions · 41 stateful · 2026-07-14 14:05:19 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
3.23
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,714,371 · 57 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w59w617w042w1450w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
16 touches
28 conflicts
0x0f8965bb…e238
0x34b655…2a6f
14 touches
21 conflicts
0x880fc665…31e3
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
12 touches
15 conflicts
0xaba1d698…ca26
0xd32edf…ff58
11 touches
15 conflicts
0x3de775b2…319b
0xa6afd3…d132
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