why2 reasons
mandatedestination_not_allowed
op 0 pays GD6KRVRYM73RUFFW5LLGR5EDYIVMJTZEINKOAIJNWCFV4ZBMXYYXWLA6, which is not in the allowlist
counterpartycounterparty_denied
GD6KRVRYM73RUFFW5LLGR5EDYIVMJTZEINKOAIJNWCFV4ZBMXYYXWLA6 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
- 02e888e5356ec434f602caf540dfe0deca700fd6c045e0a151283d9379d26369
- request
- 0d88745dac3eb0d18d2b02966dec3ee843f9d2b2e934193b8e44c981e61670d9
- transaction
- 8037740e843f98d88b2d9978b3a14d085250a8ab5ef5328cdd9edbf9f97e2fb2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51984
the chainentry 51984
- sealed to the entry before
- 062f2a2554e54621ac3dfe35845e020c4cdd553ce399cfe24a00c664f81e4f70
- this leaf
- 45cf5802f3ab4bcecadae27131c2da0582f08d7f3f610023e080b8230cf7e890
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fp+YL05kjCpqr2Iue6Qwz7pn1a2kwn6RAdfIynooFr85IuP8VSytaMJi2wFvqCmtQ7bb5+F8APP6BAu9iepfCg==