pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,835,479
← previous block
next block →
recent activity
Analyzing
Block #94,835,479
14 transactions · 14 stateful · 2026-08-10 17:31: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
#94,835,479
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
updatePrices
#4
0x5acec890
#5
batchRequestPriceCallback
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
execFwdPositionOps
#10
execOrders
#11
updateDataFeedsValuesPartial
#12
0x6a7a0b69
#13
setData
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…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x27353b2e…889a
0x065c9d…c394
2 touches
0 conflicts
0x919d5105…a3b0
0x065c9d…c394
2 touches
0 conflicts
0x98a0e1d3…493e
0x065c9d…c394
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