pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,254,538
← previous block
next block →
recent activity
Analyzing
Block #87,254,538
11 transactions · 10 stateful · 2026-07-12 10:49:26 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,254,538
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a5371ae
#9
setData
#10
execOrders
#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
0xfd3d8226…d72f
0x34b655…2a6f
4 touches
1 conflict
0x7b247aba…86ee
0x34b655…2a6f
4 touches
1 conflict
0xf0135bff…910b
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xfd3d8226…d730
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xcecc4dab…fd9c
0x34b655…2a6f
3 touches
1 conflict
0x239122db…dc81
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
0xfd3d8226b8…c3d72f
Audit this contract →
← previous block
·
next block →
recent activity