why2 reasons
mandatedestination_not_allowed
op 0 pays GBTS6MJZYSIW3ZVDPZ7P3NQ6BW4AKMG5T4KA3KYQJJYXF6ZSPYUUGW5H, which is not in the allowlist
counterpartycounterparty_denied
GBTS6MJZYSIW3ZVDPZ7P3NQ6BW4AKMG5T4KA3KYQJJYXF6ZSPYUUGW5H 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
- a8530c7bd9183e62e1b61b164e64d0933c4cc3e84346ee0f1fb7fcd7688c9321
- request
- 7561ae5816b1bf12283a9188b7724377dffd6e5af6f739e4ab732ed1503532b1
- transaction
- 28d80484f8601b56f416bb4f61198e9d3ca849408eea5acd8be4b4a3c45a52d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29204
the chainentry 29204
- sealed to the entry before
- f686e9c71da8396b1b20b632ebe26eb155d925935c6c6468cd33764bd8de8b9f
- this leaf
- 1c59f82251b3ac028027b6c6ec3f7adc996bebc6814ef123c05573240437c617
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QottJ1VlY105IDOS6QoKJGpKDgXhuJH4vxO0TqNeppb5Sic2IvSobszirfRy7oXCdIKXlXlUML14ipQ7+liBBw==