why2 reasons
mandatedestination_not_allowed
op 0 pays GBMPSRFYCCDTTGK2WNBSRD3MEEMXLKKWBAZLU4QVPAJQODD2KVKQRBF4, which is not in the allowlist
counterpartycounterparty_denied
GBMPSRFYCCDTTGK2WNBSRD3MEEMXLKKWBAZLU4QVPAJQODD2KVKQRBF4 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
- ffd46f7d53b3bcd01bea9b7418c4fe7e2c695be39bb0d2a117dddbb7f50090d3
- request
- 781e3f692288de9f0661536834d20933e7f4b0e1e9bb4bffb5c3942ae6cf0a3e
- transaction
- bc3f0b5272323ce1da763ff2f017136ea4c7269fffbe3006f13cbef592470d11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69989
the chainentry 69989
- sealed to the entry before
- 26639c5a755ff1469106c1187c3a65a8a4a8fce85fd45708b7e1c9eb4262240e
- this leaf
- ccc7ed054a734da19b8b8f9fc41ea75c83663088334a7572a9134cfadd589cb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cRDQlwliDAGRSLxqdwHLrzKCko4/vgKSkLAFigZnxVPwRPOPOZXJEmYBugRmPrf/fe7BGuj5gyPFz7ljMpqwAw==