why2 reasons
mandatedestination_not_allowed
op 0 pays GDQJ33D5Y3NLNIALWTUUUHE3EXCX7G6QROWQJU6MR6RN4SVKXCKNVQUP, which is not in the allowlist
counterpartycounterparty_denied
GDQJ33D5Y3NLNIALWTUUUHE3EXCX7G6QROWQJU6MR6RN4SVKXCKNVQUP 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
- 958af811de6c21f39eef313c8c24693ec1f6db8b7f506a27f765eeac5f2fff9b
- request
- 609ecffdf1ebdb783a4909e75379490f685bfda3e656420348e6343cc192d8aa
- transaction
- 3d001c30188fc1f13cfe8a7be650bce674fca7b6cf2a2a2c0a5105b04897b766computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65922
the chainentry 65922
- sealed to the entry before
- d1619233e208815585128318c6b6a0b68b740b80754a1730dbc8cd21fbb96097
- this leaf
- 4c9fe0fec02a200bd4f4be03c78147a74fa133e408870e71ed240a937b672728
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZP6QQdBfOWQ5CL+wHyxNQPqdcJLeAzuJUQNcaa1YE1G+8pQMHGMg9gaSHIlp+OXx5S8eR+VqynKALWRTQnk3Dw==