why2 reasons
mandatedestination_not_allowed
op 0 pays GDA3SYOLNZZ6JYZIGOMRZMJKNWIOB4SRH2WISRRA5N3R6QSLA6FRLXOF, which is not in the allowlist
counterpartycounterparty_denied
GDA3SYOLNZZ6JYZIGOMRZMJKNWIOB4SRH2WISRRA5N3R6QSLA6FRLXOF 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
- 0e1ab3ceeae590b3fae32c793ecd93a5d5dcaf2de69eb52d0117ef41cd548ae6
- request
- 26f09e18d8e7561b0bddc5f31eaa04d7ad64db32806ec5590b489ee6d48d5866
- transaction
- 40bf934c3b7106b659a86ca51e9d920fb2045ce762631a116db2b3c37c7a945ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65630
the chainentry 65630
- sealed to the entry before
- ebccae55b2d3d694960ec905d9516252a8ec230c5cfcaad2da63fb7b653b7a29
- this leaf
- dbbadd72a39d00175afd78981767a746de00206ce3622cdf7214aed4863fe535
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RCxfQgKE568XWsSAgHSRA4VZQpk1ZzVb/8RB7q3icE8BDfw+b8jA0LiBB1IrQmSbI8Q1KubKo3jE2wmtH8bvDg==