why2 reasons
mandatedestination_not_allowed
op 0 pays GD54DHF6O5ZMYLGYR6JSJL2FA7LMDWTAWKUZFOZDH353WF5PUUK5UDUE, which is not in the allowlist
counterpartycounterparty_denied
GD54DHF6O5ZMYLGYR6JSJL2FA7LMDWTAWKUZFOZDH353WF5PUUK5UDUE 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
- f7489b13964d2b8af8034bddb8648ecdeef609fa68fb8c387f1e08399d9561e5
- request
- 9f0b7a0004de5e15ca8d831d0340c615176e4facb23506538f40c3d5ef542759
- transaction
- 8ef6b9c97ffaaa99d461c1cb2366ddc5447a052def57321c8e6def2a9146631dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1811
the chainentry 1811
- sealed to the entry before
- 6d773a85ef5a31b45253a8ded0469bdd633844818388386539a5299ecc0d0b2f
- this leaf
- 3ee27ff04ce5047b4b2bc8c835baed44ee9e6ea46b5fc5a29e4d6eec8118bdf9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CpCHCzBpJn37CMkdHFZngT2pFM2TCAnpP6V0dgnABBGm76zCj/pAXk1bDSZdX/b0O4vFZItRuLtZuuQrXRp7Bw==