why2 reasons
mandatedestination_not_allowed
op 0 pays GDURCEWUIDJKXP2D7Y6DPIWQ5TBF5QTL2Q55W5LS6A52X6KGJOFOQJPS, which is not in the allowlist
counterpartycounterparty_denied
GDURCEWUIDJKXP2D7Y6DPIWQ5TBF5QTL2Q55W5LS6A52X6KGJOFOQJPS 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
- c8a5ebb92eea681523c27d346df3c6bcb98c0015e0cbcd2afd00daf337c7ca7d
- request
- 4ef25d8a99a17df839ad3ad53c2e7a0dc15731061aa80c51fd60c1ba49bc91cd
- transaction
- 619fb4b76b4eee3aaec4f52a10cbff9077f57bd673b214a12ec00f1187b8b7bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70693
the chainentry 70693
- sealed to the entry before
- 1840a8cf5f81e315cc6f6ceab930213559d98678fcd63eaeeef68257173a3f44
- this leaf
- c623fb529fac39298f422029950c017f8178e547cbb3caada8dfed771cc06a08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OmwamzreWl5SIJHymooTAQ8vekoKu/wTqbrNv7LZ87jDih8rndUB6ncBELxo882tlsnPYNsmN0IYmlFa+OqIBg==