pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,622,756
← previous block
next block →
recent activity
Analyzing
Block #86,622,756
13 transactions · 12 stateful · 2026-07-09 12:25:43 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
#86,622,756
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
artefact_keep
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
claim
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
0x6a4f93bf
#9
setData
#10
execOrders
· blocks 1
#12
0xc7e3ec2c
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1941b441…5889
0x34b655…2a6f
2 touches
0 conflicts
0x1b7fc455…f90f
0x34b655…2a6f
2 touches
0 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x259f3ba0…a139
0x34b655…2a6f
2 touches
0 conflicts
0x30028013…920c
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity