why2 reasons
mandatedestination_not_allowed
op 0 pays GBFUVNQZRJ64R5OONM4KVMB3Q5WATFI5HX3Y6FDOLEEEN6JCL3ZEGLVT, which is not in the allowlist
counterpartycounterparty_denied
GBFUVNQZRJ64R5OONM4KVMB3Q5WATFI5HX3Y6FDOLEEEN6JCL3ZEGLVT 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
- 22c1dceb3f7b979790a4de725c781f5d54e27bec8be302110b5fd2b65d06b974
- request
- 3c29e0355fbe07ffd7e5f0373c303c0b700936bd97d9232e3f30eef55960dea0
- transaction
- 20f98b3ff44adc9109561d23cb6fad479f0d4c62e946a80b94d64bb1579a5c8bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26529
the chainentry 26529
- sealed to the entry before
- eb725778412a256fb43b3a2bc746b6efb46689a6a050dd50f0b7b3910a3fa3eb
- this leaf
- 4ae9f01ceeec34c2c18cd27fda2346f7ec2c4595b15d30ea9403c6eadb49f2fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vpQP6jct/w2lZ/ICnyR9cOOLkc7EXid73KqWXoOYYdrKVlF1TFnjK3U4qQJWB9nFAjwViWbet4tA1qauAFJKBQ==