why2 reasons
mandatedestination_not_allowed
op 0 pays GBQBWAZUWDLYS5AYQX5VBGL5DJXYSBSVPUFV5EY7ERQKC6J6YANXLSNP, which is not in the allowlist
counterpartycounterparty_denied
GBQBWAZUWDLYS5AYQX5VBGL5DJXYSBSVPUFV5EY7ERQKC6J6YANXLSNP 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
- 70f9553935f7f01a73acaf43cae8bec7a53cc38cd09e30ad33498e6cc4545ab2
- request
- d13563c0969b5ee6d38fbe51e2197a29faad20357352b4e68d15ef550c6c17e1
- transaction
- 772bd03bd78943b53f40bb71aa7b1e0719a02076c3d08ac943720a4f4c88293ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44440
the chainentry 44440
- sealed to the entry before
- b14be160f435eadc392877083cae3b66196c846dda1e94e1a14624b13bb4eaff
- this leaf
- 6192e2b4fb1d453e54c9c7bfddaefe77e11d784b6185e3bbd07cc1774fcaa989
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zvi4VlJF5RnhpdjXKKjRQQlT/PZ9tEHkgemutuaGOK8sEUJ8tUi+hbI6SxMHNSFa7W2glzTpHTxjX2MCmqZxDA==