why2 reasons
mandatedestination_not_allowed
op 0 pays GBZS5EE4ZVTWMPGW7UDCQEKAGHNKZ6IGRNWJLTS4OFEIWTHQB4WE6GTB, which is not in the allowlist
counterpartycounterparty_denied
GBZS5EE4ZVTWMPGW7UDCQEKAGHNKZ6IGRNWJLTS4OFEIWTHQB4WE6GTB 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
- 9bd3b4f248a24cb35b44c9af04cd32d8f6e4875d50e4ec1269ecc15def0c0ab4
- request
- a1bf61aead891be43effca15fcd501a1abe5d69efa177857030eef8954e079d1
- transaction
- 1e798e5d49dd75befcd3f4c072f1f9f01ca29d2f9dc2bc12caa67621caf0ea52computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21169
the chainentry 21169
- sealed to the entry before
- df4160e3b0cc56b527082f38fc40896b843c9f41ecf4c1d99a6906805eb5a73a
- this leaf
- 76c008bade29d1de9abb06d2a99783dd73917403a68317972ce71188be6517d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3IyYoc0mCFVylro4ItLdu5cECODsEBsZdxVmPuI54CVR7Py4/bwyY1g1njtV70WPxajGbOW7Z0/YqOZEUVGbAA==