why2 reasons
mandatedestination_not_allowed
op 0 pays GDCCQNPHDVTKBTYUVIAESEF4I3L4S5TH7SIUU3JAO4OEJBCLVLPZ4LVK, which is not in the allowlist
counterpartycounterparty_denied
GDCCQNPHDVTKBTYUVIAESEF4I3L4S5TH7SIUU3JAO4OEJBCLVLPZ4LVK 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
- 2306452ce9570aee68b219b12224e9f418e97ee0187d0ac99aca307dfca71fe1
- request
- 69cba33ddec821f0d9f3957e7786a5fe2f705ef46028cfdac65754645517d83e
- transaction
- e922b249fc6c6ec2ae0f03927d85600888ae783b1f614bbc7244803529c77215computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7290
the chainentry 7290
- sealed to the entry before
- add096b87c1eea13891230250f811a5729595f7f8223345080de30e054eb2a93
- this leaf
- 8465ec912b2f405eae73849f24999ad6931166725e2f319b9396aba7e9b94160
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8yJjdWFbCQUSxDcneneMwMq0prKRyhxu+89zJw5SMpKlGIIbGl2ty8DD11vxu69OWoKFHl/dGdv3YzSuRPXMAw==