why2 reasons
mandatedestination_not_allowed
op 0 pays GDBT5JSGEB7KLVMEPWTULREWXA7UK7UWU7M7ZH2LLMJ7WVA6KND2CTLV, which is not in the allowlist
counterpartycounterparty_denied
GDBT5JSGEB7KLVMEPWTULREWXA7UK7UWU7M7ZH2LLMJ7WVA6KND2CTLV 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
- f1fdd45e6e8fb097b6e588797d917e0a9f8da42c1b35247b649d9a3cedadbd43
- request
- c32500d2c53729f5a93d02fa4425bca89caa49e222930fcc7e9f8486f98fdcae
- transaction
- 58e7384297df1ca569faee65fccae9a57f3cb883b8fafa4d23b263197be19806computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15332
the chainentry 15332
- sealed to the entry before
- 2bbd61ca4897743e35791146bd8372b8a0d15b4eac2731cba9b30288de1d6ba2
- this leaf
- 9dbcdd0d5fc8048b63fccf6c62fbc4d61663984c20142a16534036197ee5e1b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dgsQeCKwJSglGQBWqxBtUu2MZ6dkjMOO4IM8CzBlnuY381+HBcYRZdhk5smyxQveqb5wnLysUIhfrw2coZ4CBg==