why2 reasons
mandatedestination_not_allowed
op 0 pays GBEIUKADSREX2AA4GP6FJ5WQWWGM44XUA6CWIIT4Y33PU5RQLAA7S6IG, which is not in the allowlist
counterpartycounterparty_denied
GBEIUKADSREX2AA4GP6FJ5WQWWGM44XUA6CWIIT4Y33PU5RQLAA7S6IG 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
- 0d158953818f9ea44e33184a9765b169f0530d3bcd4acb412cf942e8ad790b47
- request
- 5956a0185c65a33dcc9825cb7f926f55f12beb4a96112ba6a6e288573713baeb
- transaction
- dd0d2eeb3bb195066b9ace2148352636d2ec211135152e0cdeb323a523d78144computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34670
the chainentry 34670
- sealed to the entry before
- d0326b6ef17624318834a68c3be3feedc684a8306fb27b9bb40138a44e5136ed
- this leaf
- 1a20a85e68ed8b65caa94c066ab49e10c30758bc8d25eb404785c1592480fd86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5tbURg2wCkqvmbqjvsBYYt2KgjDS3GXmlAJzcoj7YuTEgKnmmHNy/SxJI0TJ8ElcCNV9bpAJe6LfFlKoexSVAQ==