why2 reasons
mandatedestination_not_allowed
op 0 pays GD5G7YRVDZUGI5XF5MGO3WLJZQNU6O5WCAOFGJPABK3Y4TOZSKH5YBQ3, which is not in the allowlist
counterpartycounterparty_denied
GD5G7YRVDZUGI5XF5MGO3WLJZQNU6O5WCAOFGJPABK3Y4TOZSKH5YBQ3 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
- e9196f302159c42e0a7ed87659805f869209ec091b76ef5ed8705f3df0b3b705
- request
- 9efa56446e0bd9fe3756ab3ae9043840295a30b8ec95c4344c398d5dd372767e
- transaction
- b981f95aaabe61149b841c693f98dd7014a2b914aade52e2d68e058f3c2273afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45050
the chainentry 45050
- sealed to the entry before
- 5acb8debf4c541aaaa47544974351766622dc8643f5d2b844acd152149743290
- this leaf
- bdccae16d3ce4be05dee4c979f4ebac0fa40f408eab00c65e9c82c4b57c1078b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fCY0jfbzv/TLplAK/psVt7tLnPcEKRnhB2uDcimxIc+9Dg7o0RnpoDadKIxRoywF9dlrQSebt1B+XiZv2T4rBw==