pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#77,434,385
← previous block
next block →
recent activity
Analyzing
Block #77,434,385
14 transactions · 10 stateful · 2026-05-27 22:45:10 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
#77,434,385
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6a17746e
#2
execPerpOps
#3
execPerpOps
#4
0x15ea9545
#5
0x0c7abd22
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
setData
#9
execFwdPositionOps
#10
0x3f5c179b
#11
execFwdPositionOps
#12
0x6df9e92b
#13
0x6a17746e
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
0x7c4e592a…4bac
0x1efe02…37d6
2 touches
0 conflicts
0xc8a185a6…48e2
0x1efe02…37d6
2 touches
0 conflicts
0xee205fb8…6101
0x1efe02…37d6
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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