why2 reasons
mandatedestination_not_allowed
op 0 pays GAJVGISSEVOPZVEMNYYWXPSHKSR6NAVTKS2CA56RLUV2Z6FIG7S34LOQ, which is not in the allowlist
counterpartycounterparty_denied
GAJVGISSEVOPZVEMNYYWXPSHKSR6NAVTKS2CA56RLUV2Z6FIG7S34LOQ 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
- e36591bd7f537b99bb545110c4cc740452ce1b62f223fe465945576e04320f94
- request
- cf5123eca0e7b6ea08bf6e7ba85c1ccf0d7cc5b287f3ea6a8034bfb83bb11ae4
- transaction
- 890c3e43dc43869de2811ab69a1c1d2a3636dfc2ee6fe2a306a978f4217b7b32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66023
the chainentry 66023
- sealed to the entry before
- 83a07fa8306af460fd5b45a0b1d6674df9f8c014689b51a76daf9b3e3cd8a622
- this leaf
- 5f75405e95a8c71c2669e69b026a21f34042bcad8902d68043c1e49c3fda854e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Cy811UlUd8TqlPULz+FwteAIDWybTa6+Q3uNvRAUElmyi6v4qSqUwQrMjvlhph16XAbjs22fcdoRh1tec6exDA==