pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,525,138
← previous block
next block →
recent activity
Analyzing
Block #85,525,138
13 transactions · 13 stateful · 2026-07-04 10:19:47 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,525,138
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
execFwdPositionOps
· blocks 1
#5
batchUpdate
· blocks 1
#6
forward
#7
forward
#9
0x6a48debb
#10
setData
#12
0xc7e3ec2c
#8
0xed82b078
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd819e0f5…32f3
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x7d3b04a3…f29b
0x34b655…2a6f
2 touches
0 conflicts
0x9916a36a…514d
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
0xa20a130ca6…b85d59
Audit this contract →
← previous block
·
next block →
recent activity