why2 reasons
mandatedestination_not_allowed
op 0 pays GDYPSAZOZZZ2JO5KYOXKZEVAGVY2PAMMQZDOCLQXDOZWUDGVDFB2QTXZ, which is not in the allowlist
counterpartycounterparty_denied
GDYPSAZOZZZ2JO5KYOXKZEVAGVY2PAMMQZDOCLQXDOZWUDGVDFB2QTXZ 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
- b56e19f20fcc9ac3ef2e9c1968f82dd2577d4c2a2fd5db6351a52a78c2066397
- request
- 625a7e1eeaa274ad8dc804ccde724b0edae3aea7ffb1354e32fb84102fb1eda4
- transaction
- 08b0582fa42ffc42d7194aca977c14846a31c21d3a50f00133f57f3a8b7a2ed7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77617
the chainentry 77617
- sealed to the entry before
- 15853c00a2fbd23d2e49fd13e25e241b849bd3fed7ac650bbbc6bc265a66e828
- this leaf
- bf3b66f5b7864ca848e95b5e3d51d14d5ad53cb6a151786c1da614d0077bf918
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4UMJvHYp7K76isjQnCJOJTkBUN4Tf2kMTrcDQZSv1IEIOmiDz+ly0rpSeKJscRgB7Vn5Zg+Eq5bJErTfmE8qAg==