pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,061,058
← previous block
next block →
recent activity
Analyzing
Block #87,061,058
12 transactions · 7 stateful · 2026-07-11 13:15:34 UTC
Parallelism
83
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,061,058
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOps
#10
0x6a52426e
#11
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x039c2f44…9ac7
0x34b655…2a6f
2 touches
0 conflicts
0x1febc2d0…0136
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x3880405d…db2a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0xa08f40b255…099a93
Audit this contract →
← previous block
·
next block →
recent activity