pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,159,697
← previous block
next block →
recent activity
Analyzing
Block #88,159,697
10 transactions · 9 stateful · 2026-07-16 15:44:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,159,697
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
0x6a58fccc
#7
transfer
#8
setData
#9
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
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb6225cbd…94e1
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0227484c…b689
0x34b655…2a6f
2 touches
0 conflicts
0x1282d637…5ff4
0x34b655…2a6f
2 touches
0 conflicts
0x6a404b30…77b6
0x34b655…2a6f
2 touches
0 conflicts
0x9a6d7d87…3f0f
0x34b655…2a6f
2 touches
0 conflicts
0x9b2d3bee…8eeb
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity