why2 reasons
mandatedestination_not_allowed
op 0 pays GDZWIUXCG37ESMDXQFID5FYLPJT3NSZGHY7QSAVY6I2CJHMKDPLHD4TF, which is not in the allowlist
counterpartycounterparty_denied
GDZWIUXCG37ESMDXQFID5FYLPJT3NSZGHY7QSAVY6I2CJHMKDPLHD4TF 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
- 20c7a9392e28ef66b91c331a70f2e2edaf30e36c0828a30b44a626a94fe1d15f
- request
- 789640046c9d00839f809f3f31f3d20a3fb723184b1c08eef75f750ed95ed51c
- transaction
- f9229ea9c9d662eb4b03bf8748b97efbf7e9fec4728805f54b23b19302bc6659computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42982
the chainentry 42982
- sealed to the entry before
- 659253343696afb4bb97b8f380bd0a47fbf5eb30fc3e153ae2df400036aaf67f
- this leaf
- 75b4b313dee90be73fe1833cae565ec45b13fbe875d70fc1986e265573ee5f69
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YeH5MBvkWYf53Ar3xyBiBalULErcwWQB2ajQOjAmksu7bx0rdsK1+mBayh/J+MNqrGRiuD+7WstghghTCcFQAQ==