pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,825,960
← previous block
next block →
recent activity
Analyzing
Block #85,825,960
13 transactions · 12 stateful · 2026-07-05 19:44:09 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,825,960
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
#2
0xab083028
#3
execFwdPositionOps
· blocks 1
#5
transfer
#6
0xed82b078
#7
forward
#8
execOrders
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#12
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x20729281…b662
0x34b655…2a6f
2 touches
0 conflicts
0x2523e3b9…bfbc
0x34b655…2a6f
2 touches
0 conflicts
0xebb3b9db…8172
0x3bd359…433a
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
0x08e8f2c94d…1ca11a
Audit this contract →
← previous block
·
next block →
recent activity