pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#81,634,674
← previous block
next block →
recent activity
Analyzing
Block #81,634,674
15 transactions · 11 stateful · 2026-06-16 09:43:26 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
#81,634,674
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x1e2208…50ec
#2
updatePrices
#3
execOrders
#4
execPerpOps
#5
execPerpOps
#6
batchCancelOrders
#7
0x3f5c179b
#8
forward
#9
updateDataFeedsValuesPartial
#10
0xec020d…d64c
#11
0x660d3a…64c0
#12
setData
#13
execOrders
#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
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x38b5bf24…bb9c
0x34b655…2a6f
2 touches
0 conflicts
0x43884b7a…de63
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