pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,722,313
← previous block
next block →
recent activity
Analyzing
Block #87,722,313
11 transactions · 11 stateful · 2026-07-14 14:58:33 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,722,313
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#8
forward
#9
0x6a564f10
#10
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc893169b…6d75
0x34b655…2a6f
4 touches
1 conflict
0x176771f9…c1a4
0x34b655…2a6f
2 touches
0 conflicts
0x3e950538…2259
0x34b655…2a6f
2 touches
0 conflicts
0x48719cbe…5484
0x34b655…2a6f
2 touches
0 conflicts
0x50e54461…beba
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
0x07bb3f5a12…2d617e
Audit this contract →
← previous block
·
next block →
recent activity