What phenomenon exactly? There is exactly one problem here, and it is a UX problem unfortunately. It was previously discussed here. It is unfortunate that the result can’t be inspected in a good way, but I think this is being worked on.
For the sake of completeness, let me briefly explain the problem. The tools out there are not fully finished, they fail to make the connection between the name (nm_....) and the address that the name points to (ak_2g2...). But I can assure you that no tokens were lost in any black holes. The transaction is here it was in generation 220327, so let’s just check the balance of that recipient account before and after that generation:
(aeternity@localhost)153> H = 220327,
(aeternity@localhost)153> Addr = <<"ak_2g2yq6RniwW1cjKRu4HdVVQXa5GQZkBaXiaVogQXnRxUKpmhS">>,
(aeternity@localhost)153> {ok, PK} = aeser_api_encoder:safe_decode(account_pubkey, Addr),
(aeternity@localhost)153> B1 = aec_accounts:balance(element(2, aec_chain:get_account_at_height(PK, H))),
(aeternity@localhost)153> B2 = aec_accounts:balance(element(2, aec_chain:get_account_at_height(PK, H+1))),
(aeternity@localhost)153> (B2 - B1) / 1000000000000000000.
0.1
So, no there were no tokens going into any black holes, but rather exactly where they should go 