why2 reasons
mandatedestination_not_allowed
op 0 pays GD7F7LE4FHUPYD4RU7R5KZNAAMVWBOTBEEAE4XJJA5SZ7KWEZRKYQ6IW, which is not in the allowlist
counterpartycounterparty_denied
GD7F7LE4FHUPYD4RU7R5KZNAAMVWBOTBEEAE4XJJA5SZ7KWEZRKYQ6IW 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
- 530762b0fb7b3c45a6090695fb9e0e5bf54eb748693487788b123c45ced86f72
- request
- d602c5e83ed6593f17f624f7882720b79190b6df282390aab0dfcf5f2bf48264
- transaction
- dd9541c79aff7809907238b0ce0ac966c59ae00b2cbf9823f1fc825e7ea9ea9ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17268
the chainentry 17268
- sealed to the entry before
- 4a9c61d2f24a1bc7500529abd975fccca858bef0660df74ac5e66321c3eca570
- this leaf
- 6147a172e9312254f646c3eb96e1e346016c411747b3e3d0452e81438bb8597f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NP14rOK1igkb/s/W20kD9eHJNCm+xo3QK8fGRXlTpWHcJ7p+ZaHppw+OFQRkyAkRcbYrxegkO5x14/hjPJZqCA==