why2 reasons
mandatedestination_not_allowed
op 0 pays GD6YF56NZUL5AFOVQNKVRIOTFMXYT3ZO4LM4QZJ5ODSK2YYLPIJ5BHHK, which is not in the allowlist
counterpartycounterparty_denied
GD6YF56NZUL5AFOVQNKVRIOTFMXYT3ZO4LM4QZJ5ODSK2YYLPIJ5BHHK 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
- 1ff6d1cbb7973285a8f43d6100200bc26ccd6490e1cb9c81034779e850d99595
- request
- 47982c1c1ab61788b1c4e7c015f63fcc0eb162ab4f425755a8259f22fbfc199a
- transaction
- 73573c37828b7ac55ac4746a13df4278fc5f6ffce23981d3a5c0bd34052f64b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24243
the chainentry 24243
- sealed to the entry before
- 4c29528de33de4ba1a9fd982f9a3f186de792a152af2ffd70daf646d7a4b9f07
- this leaf
- f524026baae0d0de044ce3bd843c8d4e2f6ec95645bbb11013fb94f2cb8e2b9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9SDCaQAul/2HzoUypKT+7mUe93h6X+eMcGY8XcCWm9xSGIa4HlJoAi56kBulxOesbaBRQj2/RFMKdFNl3UpzDA==