why2 reasons
mandatedestination_not_allowed
op 0 pays GDVT2M4LUYMLT7HVFQUWFHHTVPOKTLOPUDNYBM6YUIIZVMGNLSWXAWXG, which is not in the allowlist
counterpartycounterparty_denied
GDVT2M4LUYMLT7HVFQUWFHHTVPOKTLOPUDNYBM6YUIIZVMGNLSWXAWXG 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
- de8c151b7ca69269c04554e1d04b65a8de0999c46d58ded79d80c4c2cdf55744
- request
- d3d909ed194fac0ed249ba04902bef10eb4f6cb17cc17aedcfd888752232fcc0
- transaction
- 5be3a11e70b3906fc01b66f7e2eab4024a2e0601c2164a5f81668c2a98767c38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54542
the chainentry 54542
- sealed to the entry before
- 98135da4ff5ef8f28b24e0226cb4e1090b56684c17f8e9d117fa024f0d107dce
- this leaf
- 3c1b46adcfc908d9f64aa9c748805d020a5344e5931ed21d3196c7e910fb14e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EPn0ysvQNqHfb7UcY+MGyPGJx1ZBqTPM6kEzU24jTHafDOs9qm9Gmx28MOmDf7qZW2TNFsND8VcyJLyRXzvqAQ==