pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,427,369
← previous block
next block →
recent activity
Analyzing
Block #84,427,369
14 transactions · 12 stateful · 2026-06-29 08:21:16 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,427,369
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
execPerpOps
· blocks 1
#5
0x6a422b74
#6
redeemDelegations
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
forward
#10
forward
#11
setData
#12
execOrders
· blocks 1
#4
execPerpOps
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
12
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81c5483a…59e8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x3405238a…68b6
0x34b655…2a6f
4 touches
1 conflict
0xc7f9fe22…ed22
0x57ea24…2cec
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x63d273cc…f2ec
0x80f006…d585
2 touches
0 conflicts
0x63d273cc…f2ed
0x80f006…d585
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
0x81c5483add…3e59e8
Audit this contract →
← previous block
·
next block →
recent activity