why2 reasons
mandatedestination_not_allowed
op 0 pays GDPPW7CZLUX7PHFVOMYGEQDK7PQFAUBFHIF3MQVKAVQSOI2W45LHOJ6K, which is not in the allowlist
counterpartycounterparty_denied
GDPPW7CZLUX7PHFVOMYGEQDK7PQFAUBFHIF3MQVKAVQSOI2W45LHOJ6K is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 6f966f21f4a1da72fbecb4e543e41edcfbcbb0e1e15ec00cca5a9d55251c0142
- request
- 44e55e4444f47c433d135f8fd4bc4b4646ba3984c025e7d43caeb8d22228274c
- transaction
- 053eb81938efc339475df63aad983a8bbda7e56c6ad9b0c334eff2e154c1dbf8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 722
the chainentry 722
- sealed to the entry before
- f2dff5cfbbe423d2bff3203cce3c187c63e921a8484687879e76ac03c2621574
- this leaf
- 5a02ece9ef9ee8c948c738dc72ac46d4dffca00feba351c238a5f975acebf79e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FpM6DntqfojbHRiwqncn+xqEct8bJipnDqM7hZzwRmGI3eyj7NcReJYedrf+qhMTfoZZH7WzzgNzpnluyXG0Dw==