why2 reasons
mandatedestination_not_allowed
op 0 pays GD7JHHWPHJ6ZVTCKYWX4VTNOSRLVWHM65XEWGJ6T6QZP6G3KXM4FXMDL, which is not in the allowlist
counterpartycounterparty_denied
GD7JHHWPHJ6ZVTCKYWX4VTNOSRLVWHM65XEWGJ6T6QZP6G3KXM4FXMDL 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
- 00ab7f83cceb813cc32ff2c0c72e298b59fea324bf9b2310fe3f4c9a45c90544
- request
- 9a3a68e24fe9bedcb33bd954270e4788b795e67fd06f89e4db8ffd6153f89042
- transaction
- 59b68d9a49cd032e93ed6d6ff9213005163845887fa4b3798344dabc63e91397computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33582
the chainentry 33582
- sealed to the entry before
- 99380407b858301f068fb891a882b86d91cb5321adfc332aedb1b570c5624e10
- this leaf
- ab76e72b98e57306968b7830825c45277ef4cb79f4b61464f5b2f4182c64f632
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EyytJzfS5AsL1q+MQyHi30jnLbCI/VRqVsDZ3wGnBv/esUy5P/G+NtdZ9aDF6PzyNvNtG1jrk5OnsLNU0SZcAQ==