why2 reasons
mandatedestination_not_allowed
op 0 pays GDJHN3ATKHJW3D33H6Q3H46V7FONEDRFXZM2AUN5BNMLMN2MRG7BGIZD, which is not in the allowlist
counterpartycounterparty_denied
GDJHN3ATKHJW3D33H6Q3H46V7FONEDRFXZM2AUN5BNMLMN2MRG7BGIZD 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
- 3d5476f6041cf52209a9f646f26e84e01689788fdb134064fbd137ebc00504f3
- request
- dc0548cca1869e97108d70bef6066334433805bb2470399bb8e0e8a0970494dd
- transaction
- e76107c3b19011c3229b3b204760e0b2462cd2ed22d0a37e2fe88225db06df6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1831
the chainentry 1831
- sealed to the entry before
- 1032e190ad74c65fcbd3f279ad6e18f017ce66c339b47379b24c43e45ecdaaab
- this leaf
- 1f90961091aee53ca99959da541083b4101563bc66af049e5fe0a763d151170e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pc/HAbf+zGPrgkCK+72K2yIiE2GTev43temBvCg03Uz5Ap5LOOzB7hCdzfNh2b7k4Z+vQh+XkoBQQwGGD7kDAA==