How about using an approach that makes it easier to understand your logic. 
use Data::Dumper qw(Dumper);

my %hash = (
     'h1' => {
        'k1' => 'vh1k1',
        'k2' => 'vh1k2',
     },
     'h2' => {
        'k1' => 'vh2k1',
        'k2' => 'vh2k2',
      }
);
my $key     = 'h1';
my $results = find_results_for( $key );

if ($results) {
  print "Results for $key: " . Dumper( $results ) . "\n";
} else {
  print "Cannot find anything for $key\n";
}

sub find_results_for {
  my $search_key = shift;

  return if not exists $hash{$search_key};
  return $hash{$search_key};
}

[download]

Avoid using nested loops without a very good reason. They can be hard to follow, better to put then in a subroutine that can explain what you looking for.

In reply to Re: using keys on hash of hash by Herkum
in thread using keys on hash of hash by alecclews

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.