pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,726,160
← previous block
next block →
recent activity
Analyzing
Block #87,726,160
14 transactions · 10 stateful · 2026-07-14 15:24:17 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,726,160
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#8
0x3f5c179b
#9
0x3f5c179b
#10
batchUpdate
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ab016af…dae9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
2 touches
0 conflicts
0x177f8108…ff11
0x34b655…2a6f
2 touches
0 conflicts
0x1f4580c0…08e2
0x34b655…2a6f
2 touches
0 conflicts
0x32646adf…e05d
0x34b655…2a6f
2 touches
0 conflicts
0x365bd58a…0eb5
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
0x7ab016afb2…a7dae9
Audit this contract →
← previous block
·
next block →
recent activity