why2 reasons
mandatedestination_not_allowed
op 0 pays GDEM6ZDA5M3NVW2ZQZ5AOSBVXA7EIX3UY3URS75JMGQ4BIKS2XIHMKM4, which is not in the allowlist
counterpartycounterparty_denied
GDEM6ZDA5M3NVW2ZQZ5AOSBVXA7EIX3UY3URS75JMGQ4BIKS2XIHMKM4 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
- d6653dd3569f5401ec875898af45b022047c0c8bd9e259598393b31cab647a32
- request
- 1768027b0482e16739f3e3c52c18f569edbaefa1d881965d491218684481c169
- transaction
- 6febb2e3e6f2f9fe0b483778c113a1a452b2ae4e3c8c927f669d93c6f7834f02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66852
the chainentry 66852
- sealed to the entry before
- b157e6a325e4ffe0445c8d1b18cd1b01eb39e6cf2d4eb5f4c8b37f9f678ed986
- this leaf
- 54ff93d23a82bddc83490d4b51c14962a0aedf23166592eb9a7ca249805b320b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SVYWCx8dvI2EmQtjKaKG+PRyug4wvlg+5U+yZXZPTXFe9+EOnb/g2N5jQO/n+oeqmPgv3KjL2hoFXmY+D1ZkCg==