why2 reasons
mandatedestination_not_allowed
op 0 pays GD5HVUONWSOGPITVOMSWCXYSR6RKDUH6QJ4SIDNBOTL3OKAMVMC4PEAA, which is not in the allowlist
counterpartycounterparty_denied
GD5HVUONWSOGPITVOMSWCXYSR6RKDUH6QJ4SIDNBOTL3OKAMVMC4PEAA 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
- b84b6840bd1e1b3a3ae71d326b39c71e3815d85d3f5588440213ff42e2e71376
- request
- 687f26f61244d94ee8de5e5a7cd7a288ea2407231f1224baeafe8ab27dfb1c45
- transaction
- 43daa78b94e63aea6b132197f25403c956d44aa6d1ae1777677b8e27c07c201ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62590
the chainentry 62590
- sealed to the entry before
- 90778e6645e993ac09a3b3209f0b67dd7e5d9cec0ddb44fedd3e870afd801467
- this leaf
- d10213f5f26237127eb19715da324c998ce7ea8efac993193eb92f310a640512
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D1kdJpgGtR/QTS2VIhY3jTInc/dNe05dcK0caW8z5VhMZm4qaTEbVpBTPkj7UFiq1/oEP6hhea/4YkMwkcNiBA==