pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,910,655
← previous block
next block →
recent activity
Analyzing
Block #86,910,655
11 transactions · 11 stateful · 2026-07-10 20:30:41 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,910,655
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
0x5a5d9a99
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
transfer
#9
setData
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e942750…9953
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x027ebf1c…3880
0x34b655…2a6f
2 touches
0 conflicts
0x04105a34…6eea
0x34b655…2a6f
2 touches
0 conflicts
0x0690c5d3…c8ea
0x34b655…2a6f
2 touches
0 conflicts
0x1ef60f48…6237
0x34b655…2a6f
2 touches
0 conflicts
0x22bc4ea4…5c8a
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
0x6e9427506e…729953
Audit this contract →
← previous block
·
next block →
recent activity