pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,872,854
← previous block
next block →
recent activity
Analyzing
Block #85,872,854
14 transactions · 10 stateful · 2026-07-06 00:56:30 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
#85,872,854
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
transfer
#2
0x785f5745
#3
execFwdPositionOps
#4
forward
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xd6101d…e2ea
#11
0xf50c5b…d98d
#12
execOrders
#13
execOrders
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
0x65f7a340…e215
0x0c65a0…0852
2 touches
0 conflicts
0xaf41644f…8f2e
0x0c65a0…0852
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x5902106e…27f1
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
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