← previous blocknext block →recent activity
Analyzing
Block #87,625,054
39 transactions · 36 stateful · 2026-07-14 04:08:01 UTC
Parallelism
56/100
Blocked
61%
Avg conflicts / tx
2.87
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,625,054 · 39 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
1w02w13w24w07w08w19w210w011w112w213w314w415w516w617w718w819w920w1021w1128w1229w133w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x08330b36…ae29
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
12 touches
15 conflicts
0xed59b1cd…8509
0x34b655…2a6f
12 touches
15 conflicts
0x49f75237…44f4
0x34b655…2a6f
12 touches
15 conflicts
0xd19c9d38…b459
0x34b655…2a6f
12 touches
15 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
12 touches
15 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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity