why2 reasons
mandatedestination_not_allowed
op 0 pays GBXAHP6O2FNONHWLYIZPYCR37HD75ADTKOYVTCADCQ2ST7KDBUE4DM5E, which is not in the allowlist
counterpartycounterparty_denied
GBXAHP6O2FNONHWLYIZPYCR37HD75ADTKOYVTCADCQ2ST7KDBUE4DM5E 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
- c0017840bbabc3fd3257eacb987551a7a64d2287d08d3b0b4e8adb5acc1b36bb
- request
- d41b35242e9ddd37fa44f02fece46e366e06adb1802824b2dc94c3b595fb7f1f
- transaction
- b904230c6da1b50a4a2ac606c27285ca3bd17532d9e7a0b7b4a24c5c05f08301computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28630
the chainentry 28630
- sealed to the entry before
- 21168af735e60622fbe48f329e6a24c4b957088f9cbc4d5c6e60aa3b183c37aa
- this leaf
- e91a7458c0168952473361c51484d6fe4e2c63a249b55a4b21d6bb2a454d2438
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vPfpzX33OyQzmogKNGsyfqX3R/1kUNs5M3ol4LJ5y7BQeZydXVBuoyoVTv5pdFcmYIj2H+iTugNkMfFFXa9wBw==