pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,250,081
← previous block
next block →
recent activity
Analyzing
Block #85,250,081
11 transactions · 10 stateful · 2026-07-03 03:48:07 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
#85,250,081
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x6a47316e
#6
execFwdPositionOps
#7
0x3f5c179b
#8
execFwdPositionOps
· blocks 1
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac6f24e7…c98b
0x34b655…2a6f
4 touches
1 conflict
0x27f2c756…0ffc
0x34b655…2a6f
4 touches
1 conflict
0xe25c0d59…97ed
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x3a7091da…f2eb
0x34b655…2a6f
2 touches
0 conflicts
0x64e78a02…e340
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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
0xac6f24e767…bec98b
Audit this contract →
← previous block
·
next block →
recent activity