pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,354,164
← previous block
next block →
recent activity
Analyzing
Block #86,354,164
15 transactions · 13 stateful · 2026-07-08 06:29:06 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,354,164
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
0x3f5c179b
#4
batchUpdate
#5
forward
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a4deea9
#10
setData
#11
0x8c5e82…85c7
#12
execOrders
#13
execOrders
#14
0xc7e3ec2c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x161eed65…cb3b
0x34b655…2a6f
2 touches
0 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
2 touches
0 conflicts
0x1d17ea2b…cbf5
0x34b655…2a6f
2 touches
0 conflicts
0x1e7e4246…4872
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.
← previous block
·
next block →
recent activity