why2 reasons
mandatedestination_not_allowed
op 0 pays GDJGSSX2SEGQL3LSLHWSFUKSS7WPUIIIGQGRFKO4D2OHXI7HWNUZ4SOB, which is not in the allowlist
counterpartycounterparty_denied
GDJGSSX2SEGQL3LSLHWSFUKSS7WPUIIIGQGRFKO4D2OHXI7HWNUZ4SOB 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
- ce4b8530ec32f6f63ac65125361b0b32bf409bf08042c3cc7f65ac9fa5dd5f33
- request
- 768bb7778f62883fb9b68e00e7908f2a31d878e4aa0acf2d04a15662f536f68d
- transaction
- 70a3ee55bd9f6fcb64dddd733b648ab8e13b5af8b3e47984f7b08c6edd8ddb15computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45558
the chainentry 45558
- sealed to the entry before
- c59d7ea6046fe22c55ac209375e34bc8afbbdd7376333fb75081249fd4c16331
- this leaf
- a976eeaed3251e1362d73295e9e13071cd6a624fbf297277f61ceed8b3d63324
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9LbsrM3eknY9c8YPjmJXqiY8iyx1wIcvK/7aqBF+hOLifuhzJ0IjBTRlVYYcH5LG/cJOj7uiaovYUzpXRBmJDw==