why2 reasons
mandatedestination_not_allowed
op 0 pays GDU5EPR6U42U5HUR64XQWSTWWKCAIPXX7EED5ZMG73ZATYAY62GQ5SQK, which is not in the allowlist
counterpartycounterparty_denied
GDU5EPR6U42U5HUR64XQWSTWWKCAIPXX7EED5ZMG73ZATYAY62GQ5SQK 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
- 1726f818fecf481857aae693b72981504b31b83396f150ae9cc565410787e528
- request
- ca48803cca09dc9d8c444aa8e5cb410527ce527e3c537133a3c722ac420ac4bb
- transaction
- fd6d62b691fcf25a2f28f3762e5369887af2d484afdaa285000d88b620d2a33ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2676
the chainentry 2676
- sealed to the entry before
- 66de4d163df4f361588010df762b6d78100d2ab8710b0850625245447e845f26
- this leaf
- 2962af063bc13ad6c46d4c00b814f763c1c8018388916150d33c117c1c17fb3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eN9DZJ/ju6Sdi/DxT9sIO42ExgSI7WC3WDSf5n0ZKCASh1yJRdimJ5PunsixUEapt4/aYPALcOKYou0WuDf6Cg==