why2 reasons
mandatedestination_not_allowed
op 0 pays GBYZBOV66MFKJYYB22GZEZQKYTMF4G2XMV56KUENW44PLFLWKF3QZHDE, which is not in the allowlist
counterpartycounterparty_denied
GBYZBOV66MFKJYYB22GZEZQKYTMF4G2XMV56KUENW44PLFLWKF3QZHDE 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
- 9cd98a8fc44d01521fca1fce4f31123f9fcfe72f1a844ccb41d442eef694cfe2
- request
- 8a156dd6b96c5474d88be6c200640ad2681928c9a94d5032b953e1b0fe292d2f
- transaction
- 35e54c625f5105febbeb2aefdf59714af9d0d1a98b8a7169eec09e0fa018bb15computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29052
the chainentry 29052
- sealed to the entry before
- 98588e3175a3ac81cf027d840b59ef39d3a0ee679dd8428d2baadce9cf86fb61
- this leaf
- 06d6c1a09ac717745d3d28467427af1e26f12b98f5c4540315efd8583105529d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rUk7qJ19PEXJDtdZ6Uhiga2ll6d458GWWMLOsefCnTeGothLXrZNs1Yreeyv714vN5aa1PutQMvkX3kjlYJiAQ==