why2 reasons
mandatedestination_not_allowed
op 0 pays GBUEDHMZFRV4OTDENT5VPAEMSDVQPFNBZ73OUQD4OLFQHU37JMDAQCZD, which is not in the allowlist
counterpartycounterparty_denied
GBUEDHMZFRV4OTDENT5VPAEMSDVQPFNBZ73OUQD4OLFQHU37JMDAQCZD 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
- 1c0e05f388c3c756d938c0eb55f93cac55ca5ded14ea1f27163057d26e86a521
- request
- 6ab8a30ccdbfba2a4003587b8a06e5942d89e4f1526ecae51ce0dc1eb5d12d90
- transaction
- d9db79e43c0e19bb2fb8f60d8488ed361d1a8276f97d468a9aa961a15857cf9acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22359
the chainentry 22359
- sealed to the entry before
- 82ead726b24151b20610e986a39bb764cde7eaf32ae784faa26fd4f6ab9db4ba
- this leaf
- a4dff14822daec29b9082970b1ad24ef0f2a7521999adccd33b8c8d043685a58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z4RnKSp6h3nx/q9+tNQHkqomJsHGLCFJ8ArLANuqrIMGex8TRBEYKlaMe6o1lq92HP5dCXog/fiPDdkbv8s9AA==