why2 reasons
mandatedestination_not_allowed
op 0 pays GD5HQXMEV6VOFTIWQFLSX6KJ62P2BN6HVYCT2VFBC4CWGFWQ3JVTZJLM, which is not in the allowlist
counterpartycounterparty_denied
GD5HQXMEV6VOFTIWQFLSX6KJ62P2BN6HVYCT2VFBC4CWGFWQ3JVTZJLM 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
- d997f7ad066eb963c2002036494f760c6ad35032585848d194b84e432bf3286b
- request
- f9d4a170361c22f2f493d6befe6684d62c466b23b151743dccc9f4a73ed3ef68
- transaction
- da5c5945cbbdd3b3373534e6e3d492fd589e088df1b18725f7cfc6e3dc36b97bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13513
the chainentry 13513
- sealed to the entry before
- c945dac5e000cb478c9e49d85efa0b995676932f6b61e348a667e6034740bc24
- this leaf
- dc03b8a7b5d6ce2cf3ae77f3754bc166015614dcd329f39ac8baddf94cd35f40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wXRS5DltLa+4HBEsHeKSiAlj4WnGB2zw9GD0N66gqxauqGi8hWG11OACfUpjV4zxsAIgmdIspIifi0jWmOjOCQ==