pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,570,386
← previous block
next block →
recent activity
Analyzing
Block #82,570,386
15 transactions · 10 stateful · 2026-06-20 17:44:57 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
#82,570,386
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrder
#2
execOrder
#3
0xed82b078
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
placeBet
#8
forward
#9
execFwdPositionOps
#10
requestOwnershipHandover
#11
setData
#12
execOrders
#13
0xc7e3ec2c
#14
0xc7e3ec2c
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
0x737acb78…fce8
0x34b655…2a6f
2 touches
0 conflicts
0x8a7af3fd…72a6
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
0x34b655…2a6f
2 touches
0 conflicts
0xcf17589f…048c
0x34b655…2a6f
2 touches
0 conflicts
0xf1f2cd3e…8b74
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