pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,021,175
← previous block
next block →
recent activity
Analyzing
Block #84,021,175
14 transactions · 12 stateful · 2026-06-27 11:15:15 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
#84,021,175
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6ad2e98b
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
executeBatch
#9
execFwdPositionOps
#10
0xed82b078
#11
0x6a3fb13a
#12
setData
#13
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
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x2943be3a…1347
0x34b655…2a6f
2 touches
0 conflicts
0x33412db4…0073
0x34b655…2a6f
2 touches
0 conflicts
0x3af28546…d6b4
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