pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,124,831
← previous block
next block →
recent activity
Analyzing
Block #85,124,831
14 transactions · 11 stateful · 2026-07-02 13:53:35 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,124,831
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addLiquidityNATIVE
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
execOrders
#6
0x5a5d9a99
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x3f5c179b
#10
0x3f5c179b
#11
execFwdPositionOps
#12
setData
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x0382fe33…4c5f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x05d6ac06…2ebe
0x34b655…2a6f
2 touches
0 conflicts
0x0eae34b9…718f
0x34b655…2a6f
2 touches
0 conflicts
0x16a05dbf…0d3a
0x34b655…2a6f
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
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
0x2877f4400c…13c2c8
Audit this contract →
← previous block
·
next block →
recent activity