pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,719,679
← previous block
next block →
recent activity
Analyzing
Block #94,719,679
15 transactions · 12 stateful · 2026-08-10 07:47: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,719,679
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0xeb282f7f
#4
0x5acec890
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
executeBatch
#9
0x30a19e01
#10
0xed82b078
#11
execFwdPositionOps
#12
0x6a79828a
#13
setData
#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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6e49be70…9ea0
0x1efe02…37d6
2 touches
0 conflicts
0x0f07cfaf…9a8a
0x34b655…2a6f
2 touches
0 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x810a3aa2…0227
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