why2 reasons
mandatedestination_not_allowed
op 0 pays GDSP5UQMYHYRC7UFMUB3WGRUPE3BATOU424BUSWZUIDGX66KDSY4WUQR, which is not in the allowlist
counterpartycounterparty_denied
GDSP5UQMYHYRC7UFMUB3WGRUPE3BATOU424BUSWZUIDGX66KDSY4WUQR 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
- f35302e9d6e39bb9e41ad478cfd4b9162291550b9ee759ed5fbad88c2624c94e
- request
- 776416135a5f301f9337f179f6e5ffefb10de5d35a5bef68a3d2a6ae9a7516ff
- transaction
- dedb94c5b17092771297209c17c36e27f11b3dfb9d50ccceddc31d2ce011da78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1111
the chainentry 1111
- sealed to the entry before
- 4d39f5943ede17f210ab29c7e3675a26fdfc20492d2251684ab98fd2927fd8c5
- this leaf
- c905a33825dc045028f91aed94b8aa6c899bbe90fb0776a7cda83f5a0fb73b94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yQLEaokj01PHxHBdNi6I08qMFMjEzO++m32jjnqSclny9qKvbgv1OnnF+lkvcUqB3T8J8miagrSjQn1Av+/WDQ==