why2 reasons
mandatedestination_not_allowed
op 0 pays GD5PGNTQ572A4OZ4SHHLDFLQHLAYMWETRN4MNZJ5YPPRN3UCAE3GUDRR, which is not in the allowlist
counterpartycounterparty_denied
GD5PGNTQ572A4OZ4SHHLDFLQHLAYMWETRN4MNZJ5YPPRN3UCAE3GUDRR 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
- fb6c88575e562f019ce9138809bdd86a42ee707e0f4783b41621d847548de4cc
- request
- 5ea15bb2fec8a029cbce5634f44c72f253d939f4d914725069ff53cc419363cc
- transaction
- e93b99533c52da27bf4d7e13a09cc1033f72a8315baba193bb76aaf31db49d6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44529
the chainentry 44529
- sealed to the entry before
- ab11faf3ecb5f0bad55690c0065e9193978959608cc93ce3d978fba64ae81f9b
- this leaf
- 081556e899e2e92c43a934f7b7a682bcbd708e43e750eae7dd139a0c7d709f91
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BMeqWc1Py2hBO/cmsQr+7pSReRCLGHGbE2o0q7iGms7PbloBRzhjVN10GJXvKZqEV6XSLdj5xFgZplW5zUvoAQ==