why2 reasons
mandatedestination_not_allowed
op 0 pays GDCZUNLOYI2QZOFLBKCFCRECJIG5P3NFINLHKY6TFS4EZWIGZ2UJ3HIJ, which is not in the allowlist
counterpartycounterparty_denied
GDCZUNLOYI2QZOFLBKCFCRECJIG5P3NFINLHKY6TFS4EZWIGZ2UJ3HIJ 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
- ead7c32a2714950273c32cac1c830c3e62b417f2a9e9e7c53cc7be8759a21eb6
- request
- c639af39e081bd5a93a28b7201880ae5dbe5908fa56fd290ded5c7389a701ac5
- transaction
- b69bd5740b547eb5172d18e83c693f4eab3e315df54647a1dee06a80f0f58578computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69813
the chainentry 69813
- sealed to the entry before
- 81d55a16cf9a557809ea5def81e89e25c1dcc72b8e65c0c3e542f89ee2299679
- this leaf
- bc75d5f1ede0b8257474990c669dd5eeb03151f84671d9b272238622ff15c44e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cyuuL1yxtPkeWsm6jQJV8aE3eA0DkzeWR6wXGLuuJyKvEP4zZoXkqUHn+y5q6NFjFWFVd32XRvOwZPPWolYLDw==