why2 reasons
mandatedestination_not_allowed
op 0 pays GBJ5ZMLCSWHHW7YIHRS6S7VNVLC7TYTQN6GF23UXGQINN63XT7SY5STD, which is not in the allowlist
counterpartycounterparty_denied
GBJ5ZMLCSWHHW7YIHRS6S7VNVLC7TYTQN6GF23UXGQINN63XT7SY5STD 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
- 0318f7fc03ebcd0a999d87bc6eb4f161fe1e87f2d401d84be383b37f7ddfc3f1
- request
- 4f985ecd6bac746a31baa391af6ba76d351ce4f208ca1eeea5648df933804676
- transaction
- fa795cee818662ff50007d24f00e16daf41d77740d820b07583b8c169b3bda9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24224
the chainentry 24224
- sealed to the entry before
- eb0b4f248c8479bddc485e87fc6b30668dd56ca36686fc2611d2034842b94813
- this leaf
- a6cf05a5370b5d31fd586e59c2eb09492a95092d8f8d1c224cf2f04296c6ae66
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Y+DxsQJ9s8R9bQ75wuU4tYpZG3denSKuuPr9kPuVxkiKwm5uEB884/s9591y6xptTstG6KKscTNu+ycfrCUDw==