why2 reasons
mandatedestination_not_allowed
op 0 pays GD6WXTO6VHUEZ33Q2N35L64YF4JOL7ENYWO7TYA6B2VLR3DG5HFUCM7N, which is not in the allowlist
counterpartycounterparty_denied
GD6WXTO6VHUEZ33Q2N35L64YF4JOL7ENYWO7TYA6B2VLR3DG5HFUCM7N 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
- 6b27d43854b10ff5f5404d107df604e3ca93e075f9f9cadd3d825507477872b8
- request
- bbeaa88f432a81461c3bd218bc9304341c29992aff7fbb147639a883e2a70a63
- transaction
- 625b61f3f2bbbae4808c8cdfb938fea292942f9289f8ef6aa7a8f468276b2a44computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31397
the chainentry 31397
- sealed to the entry before
- cd56f19e5e49d8d5da19f027536a3454987d73dcd81a10b043cee56b02dabac5
- this leaf
- b400ec1982eb450139b0e535ebb9bd4c01b35f62c36bed9501b7e7f0461d698e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q2sn104nYBjjuQJq6+6q+vH5FWp/5cXkZ1HvR6VmyH+APLwAj0DxO7tqF5KgBoz6EGOJRDyQQ1WVtDXy2K/5Bg==