why2 reasons
mandatedestination_not_allowed
op 0 pays GCLHJMQUGVSX3ANZNWL6ABGHL7GUX3T7X32UE6SW6ZXDPZB76P74DSV6, which is not in the allowlist
counterpartycounterparty_denied
GCLHJMQUGVSX3ANZNWL6ABGHL7GUX3T7X32UE6SW6ZXDPZB76P74DSV6 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
- bfd26efcd90a9c948b9f7ca2e0c532fef8aa6a4d2d04e4521525f8bbd0747ad5
- request
- 1af8aabdf9a3a8f1e440f8fcd4ffb49dd07bb7b888cbb06b3faf0210f7688924
- transaction
- 5df826e8adb66d1c8afbfe9eff0e32b4c8eba92b5783dbced4f4ea68bb984f66computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9309
the chainentry 9309
- sealed to the entry before
- b325d6adfc63efd3dea225e58acefb3190d016a32c601ea1c227ee9b09a38b89
- this leaf
- ef5d46ef39546fffc22319d0ae014f97d4d7e0b21b62858b4b72e39216d11f68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LcisJx206NSan2d5XrwNtJYvQaeSqMiM97QdxH6Jz2pS34Y9ooXvNwu0oKir0IQMsx35LwB5Fxk6vmBufuG5Bg==