why2 reasons
mandatedestination_not_allowed
op 0 pays GD4BN4QB2FV3ZUH2SQR7TB757IAPHQEMJS2LOUOZMKQRGRSMGZKIFCD5, which is not in the allowlist
counterpartycounterparty_denied
GD4BN4QB2FV3ZUH2SQR7TB757IAPHQEMJS2LOUOZMKQRGRSMGZKIFCD5 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
- 58ad95c04ddaf0a7041c7a5ff7c7483d104efb8453c952bfeae83364a248c842
- request
- eb657650078099eda2c63ac872c43e77a82bc6acf01363917a64725361c0ed38
- transaction
- c9d851416674b4948dbb930fb71f787fcefb4a0149278e8a28b011d4e253294dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2451
the chainentry 2451
- sealed to the entry before
- 11b7fedf9fe0872e5ed58c9df8261eff4a55008d87c574361e7a713bb0d2f626
- this leaf
- d59387044926e36a0e29e9dcc4e9f6d59cb72543564af45c946cc7e848e23ee9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HIRvTqCFz9trmPyh5AbI3ny8UpTxtoIBapLWA9xGR8T8uh9F+AmViagRHU31OxF7h5VCucCyZJPBUHUiw79LBg==