why2 reasons
mandatedestination_not_allowed
op 0 pays GDOPYJSCKNZKXQJ4PFZ2UNOOBLKWI6N63VX3H2LYYPJNXA5NO2RXZXV3, which is not in the allowlist
counterpartycounterparty_denied
GDOPYJSCKNZKXQJ4PFZ2UNOOBLKWI6N63VX3H2LYYPJNXA5NO2RXZXV3 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
- 9749e7f734e3ea4e7f95e5a15f4929d9329e72cc8edf0c2853e8393affd7aa90
- request
- 3ebdf00a514bad12c95df3ba2ad0e6582766e47f0ec669a159c4f027fd812081
- transaction
- 8352cb1bc2bd778a20d7e5cc235da5e7bd665aba2bbab1bb89f43dec4cd892c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66075
the chainentry 66075
- sealed to the entry before
- 873449aab4591423d4284c23bfa04ff858795c3560a6b4227432fd39620759f5
- this leaf
- 53dd25e85f135539a0bec5565954410fb624be268fbf3ccfbf9fbafbaae63ee1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ixqqLKm3atez/tliCYiADSiIHyZzTScXnI0ltgrYtfAYH8Q8iaADy/nx/Hqq/v7/R8dfmrlUUuCs2J2XOoo/Dw==