why2 reasons
mandatedestination_not_allowed
op 0 pays GBUZIH4FO6LKGYWN4TN2QWNJZEUW43HIVCPI3B5MRUCPVSAAY4W6ZZHW, which is not in the allowlist
counterpartycounterparty_denied
GBUZIH4FO6LKGYWN4TN2QWNJZEUW43HIVCPI3B5MRUCPVSAAY4W6ZZHW 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
- c01e581ffbf99e346822de81a81af0c197026821f7e8fd6347420f3b0d0e9869
- request
- d82e8cb1b1009243c2f4527864e0749193adf4608a4f0c647b536b3bb38a5e47
- transaction
- d9f497ad9e707811512fae83544651c3294a451c63103076a7701591eaacd401computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6148
the chainentry 6148
- sealed to the entry before
- 15aefcd65101f625fa068846450a9f1ea04d3ce49616a050d9bb3cc8dbb5a988
- this leaf
- 06662eba71e8e97195a82a07e2cd4058284f568c6faa90f5601973a98372fe3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ldoC2/fZgNog5468/nZPTO4JdusJOXsf/gXSIKzks6j8wMOYj6n1eZdwzLyNIDqPipVqufyxdS8qarnoZE54Aw==