pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,630,784
← previous block
next block →
recent activity
Analyzing
Block #86,630,784
15 transactions · 11 stateful · 2026-07-09 13:19:20 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,630,784
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrder
#2
0x6ad2e98b
#3
withdraw
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
receiveMessage
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a4fa050
#10
setData
#11
0x8809b5…a286
#12
0xc6ebb3…3d9f
#13
swapWithBackendSignature
#14
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x009177df…4ecc
0x34b655…2a6f
2 touches
0 conflicts
0x16be067e…1565
0x34b655…2a6f
2 touches
0 conflicts
0x2c58327f…7726
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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