why2 reasons
mandatedestination_not_allowed
op 0 pays GDBI5W7QEZEJBO7K26MBFZ2H5MH7L7FDY65ODM4GZDAJWBF2N7I3XQJU, which is not in the allowlist
counterpartycounterparty_denied
GDBI5W7QEZEJBO7K26MBFZ2H5MH7L7FDY65ODM4GZDAJWBF2N7I3XQJU 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
- 821e31aa8e615899b4fa02f2a03497ce3f7769d428ba8bd944935c7a6837cd3c
- request
- 0d25557098b542c1915fbd98406a76e55306130b9a9de29304e2fc1dc21ed588
- transaction
- ef1a84e45486fe8e1f6ed2c64d980301d9e47d9fa1c2433845b100a5ed4ee3a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42095
the chainentry 42095
- sealed to the entry before
- b178ad3ad88e846dbef759f8d7c9daeaa1d4b9c34f6043bcfac9bff53a9ac755
- this leaf
- ca16e6e9e980a853e824a59fbc9592e1d13440d8464bb482eef8163bf4452a53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m5B+ajyU8fzLpuRgO4QKYXKRrzHRBP2lpAUhzFiRkWrt1ggFaxcXzRXitM0uIW+p6FR6M8RlWLkzML+7leQLDg==