why2 reasons
mandatedestination_not_allowed
op 0 pays GDGYXTP5SJ7U2ZBMHH6W36G6PR37BAEMDYKRTTPVA4RP4THUJY7AYTSF, which is not in the allowlist
counterpartycounterparty_denied
GDGYXTP5SJ7U2ZBMHH6W36G6PR37BAEMDYKRTTPVA4RP4THUJY7AYTSF 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
- 127f9e40c610b390dbaef53c3314b2c2edd33a43da9854ce0681fea06a528b48
- request
- f679429bf2b067c0f0989185667fe5f87c49b770cee2ef590838761d962d8d9d
- transaction
- 0a826eecdac136289af6c71cf3b22b4b770b53657aa51c61ab969684150957d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60712
the chainentry 60712
- sealed to the entry before
- 33825fc8145b185b4ca80874e18fc6196b1f0f8dbdddc2109ff0632f3b64f21d
- this leaf
- 411549e4623a179583e859ba3908d9a1660902f400d5c53aff563245e4b58c0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IXVGp8K5L5ZNTAHSuqmGkVikVWlUEBASmFWO9jwCfK9sH/lLZVkkzsV1ReR8x+PdkMbizwBKe79WqgXGhfvvDg==