why2 reasons
mandatedestination_not_allowed
op 0 pays GDQG3SD7UPQKMSXT6MPMX2Y7MPQTBSKNYSOGA2YMFGC2OA4M2XJO4G5E, which is not in the allowlist
counterpartycounterparty_denied
GDQG3SD7UPQKMSXT6MPMX2Y7MPQTBSKNYSOGA2YMFGC2OA4M2XJO4G5E 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
- 226c77eab9598ab3c31597e9c51568de221423a4419a392bb00a46579c497d1f
- request
- 4b2204402b0d58913b09e0e13f03a793f7793ed2afc168d6a1aecae22d2a3731
- transaction
- 6bc26e23909b3ec5ea5a644ff3631c682fd53b748524973035697818096109c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28272
the chainentry 28272
- sealed to the entry before
- a8653e12ee7b38185553d3f3d4e1bcb30ad2628bedcd0d81b3443f064773a763
- this leaf
- ea6a3dc1a8ef833355b8745eaf95c29f65fbece830cadabda339b269aff11fc3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +DZt+JgIFIFM62yjFdMyP8+6AhYSguMd7ItXDgoADtONL8cPZzOLU5kTidQqC/3Yj+GIFkeP4/6JELeADeKFDw==