why2 reasons
mandatedestination_not_allowed
op 0 pays GB4MLIX2NGNB7H2FIUEVDJNT34JDLO7RGIQPHZBOIUBM2BFJ73FHXTU2, which is not in the allowlist
counterpartycounterparty_denied
GB4MLIX2NGNB7H2FIUEVDJNT34JDLO7RGIQPHZBOIUBM2BFJ73FHXTU2 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
- 8f5162f5a4f731a71f28783434dfa570b9f8dac52bfa4bd45841ef65b4fcd93c
- request
- ac5678e115e0dd310e473d5b0a4163d9875f3b37b1b231b0f28ffaf909634f7d
- transaction
- e28e5810c7a5261fe31e6faaa45c93b857e0687a43d3109163c48d92192f0488computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76764
the chainentry 76764
- sealed to the entry before
- 8c18ea5c6e731d6e16ab2f4573590cb022bdc63cfd0cb0016aa98e89c8b269da
- this leaf
- cc6417928d3378c7969bc7d4dc0545f7409d8de4549817ef5252d1bc73e3139a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lxmPTMvCOoFqe8qHi/SIneybXyzR4eXS9G9GOKEPClo12ExqjarlLW951KByDwKljcRL4R0NdI43u5aDgCO+Cw==