why2 reasons
mandatedestination_not_allowed
op 0 pays GBXSWTKKPK3SYP673SFMPQ4CZAUXLIM5KE2CKX63SPKZEYCU4L2PAHMU, which is not in the allowlist
counterpartycounterparty_denied
GBXSWTKKPK3SYP673SFMPQ4CZAUXLIM5KE2CKX63SPKZEYCU4L2PAHMU 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
- 5abb1f3ec55694aee5162287f4a104ce995f3fb526a684f1f29a582ba659f90d
- request
- 2acc76e5d35c7cdb31264ac186090eb57291ef9984b17fcd565e3effbbe9bf89
- transaction
- 9a42b51adbbb18b31b1262164d5ffde45412e3c97db2008933edd55a4ffea51bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69615
the chainentry 69615
- sealed to the entry before
- 7e5a4392c5017bd59a8d3d748e036384a5cc083a26d11493063f92845aa4af28
- this leaf
- 6d073eae171b7e226a57e3abfd72c44ffa57301ddd23989f9e671078fa58505e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- puCOluonHJUh6hZ1u3CTrGGOceOArmcXFfmTLdckIeA9XqHwzyZZauNuc/+dW3hba5I4f5s78XLl1Arfl5lHDQ==