pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,360,458
← previous block
next block →
recent activity
Analyzing
Block #86,360,458
12 transactions · 10 stateful · 2026-07-08 07:11:07 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,360,458
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 2
#3
batchUpdate
#4
0xed82b078
#6
updateDataFeedsValuesPartial
#7
0x6a4df883
#8
setData
#9
0x2ddfeb…d3a1
#11
0xc7e3ec2c
#5
execFwdPositionOps
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x0cc95a4e…8593
0x34b655…2a6f
3 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0d488000…3831
0x34b655…2a6f
2 touches
0 conflicts
0x1469879f…f413
0x34b655…2a6f
2 touches
0 conflicts
0x1a05ade0…672d
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
0x16a8cd0cae…8827bd
Audit this contract →
← previous block
·
next block →
recent activity