pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,692,885
← previous block
next block →
recent activity
Analyzing
Block #83,692,885
13 transactions · 10 stateful · 2026-06-25 22:45:57 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,692,885
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
0x5a5d9a99
· blocks 1
#6
execFwdPositionOps
#8
0x6a3db01d
#9
setData
#10
execOrders
#11
execOrders
#12
0x50a0b275
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xfe4e62b8…9ade
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07d1dc5d…1838
0x34b655…2a6f
2 touches
0 conflicts
0x0f602203…4424
0x34b655…2a6f
2 touches
0 conflicts
0x1750f6f9…ff47
0x34b655…2a6f
2 touches
0 conflicts
0x272a391e…9c91
0x34b655…2a6f
2 touches
0 conflicts
0x487922c6…dbd2
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity