why2 reasons
mandatedestination_not_allowed
op 0 pays GDYA5JLMQJTFE36CDOQRURILF7M2MSYRA3TNMPY4JMW77GVZNRF2B7IA, which is not in the allowlist
counterpartycounterparty_denied
GDYA5JLMQJTFE36CDOQRURILF7M2MSYRA3TNMPY4JMW77GVZNRF2B7IA 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
- 88e141bf1e4eb1b412f6310a3a65f6d083c4ad564970aa5ce3070b4789655ffe
- request
- 34426642738352a5e9ecd0385fd149ace7650b9d46dc48e91b1b59d858a00c0e
- transaction
- 404a2eae092cd4bf0310c0ac0e78c60b7e96dfbf357ae816264bb353bb88dd70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64728
the chainentry 64728
- sealed to the entry before
- 3c7410e36bc07098d352411a53cd777f774556244bb60524ae24bcfc426f5093
- this leaf
- 17742b299b81ea91f5e2341b9984e5815dea01b5ff1dd16314f294383f48d3e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r3WcrDR2rdczmphPY6r+HyRJnRSPBv1I8ashKQ9d2sNF4BOY8WrsFT9cViL5W33k5gCr5oSGngLFpugIqKAuBw==