pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,279,353
← previous block
next block →
recent activity
Analyzing
Block #84,279,353
11 transactions · 11 stateful · 2026-06-28 15:54:52 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,279,353
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0xed82b078
#7
0x6a414443
#8
setData
#9
execOrders
#10
redeemDelegations
#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
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xeb6b4068…bd76
0x34b655…2a6f
3 touches
1 conflict
0xa0784dd2…0278
0x34b655…2a6f
3 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x11079779…7f2a
0x34b655…2a6f
2 touches
0 conflicts
0x11fced72…74b3
0x34b655…2a6f
2 touches
0 conflicts
0x14aade0f…0c79
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
0x9a3068dd84…9918f0
Audit this contract →
← previous block
·
next block →
recent activity