why2 reasons
mandatedestination_not_allowed
op 0 pays GBVZKVYCDS3O7RQTVIHBRVTESWGUDYCNLMC3PNSR3YPQZL5TPTNC6L22, which is not in the allowlist
counterpartycounterparty_denied
GBVZKVYCDS3O7RQTVIHBRVTESWGUDYCNLMC3PNSR3YPQZL5TPTNC6L22 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
- 0ea1f35d3c264fa52ea4ba03b8e563174191df4571bf9c941790b0423899fb98
- request
- f8ad05c1e319292f37cbf815c11a94d881c9b9065d926f2ed8a6b318ea6b5432
- transaction
- b1e87d8805053703abbc8166ff556b540a26714db8fe4099e647c05902d035cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2911
the chainentry 2911
- sealed to the entry before
- e740c0ed3233652339c6303c82703088cef83b2f2c569df24a02ed5d6893d449
- this leaf
- 3ccda70ad5c8ed50ca6a5a6e655595eef0232534e9bce24499d60820d0a62700
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YWMiXtscXGIa879+RTaYkZEhwgiyvRcKTyJ1qno7jiLrfmFbEcipkvby4FqVOj/3IWGMA4rXtpHPxnOeEVyzAQ==