pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,792,258
← previous block
next block →
recent activity
Analyzing
Block #85,792,258
10 transactions · 7 stateful · 2026-07-05 15:59:41 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,792,258
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x234623f7
· blocks 1
#4
execFwdPositionOps
#5
setData
#6
0x30f858…587f
#7
0x8f128d…28e9
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#3
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbeac5577…b913
0x62ab75…c800
4 touches
1 conflict
0x00000000…0005
0x62ab75…c800
4 touches
1 conflict
0xbeac5577…b90a
0x62ab75…c800
4 touches
1 conflict
0x73cb5554…4902
0x754704…b603
4 touches
1 conflict
0xbeac5577…b90c
0x62ab75…c800
4 touches
1 conflict
0x6d9ff366…36ff
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
2 touches
0 conflicts
0xa3fb2f06…c5f4
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:
0x62ab757c…36c800
1 conflict on slot
0xbeac557752…afb913
Audit this contract →
← previous block
·
next block →
recent activity