why2 reasons
mandatedestination_not_allowed
op 0 pays GDLV6NZH7A4UKZLUF2IGQSOCMLMKWBDM7ZU4I3J76N4IY7K3QA36Z64V, which is not in the allowlist
counterpartycounterparty_denied
GDLV6NZH7A4UKZLUF2IGQSOCMLMKWBDM7ZU4I3J76N4IY7K3QA36Z64V 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
- e42f50bf6f482839201b1164dd3ef82116c524be35b3b75859ebc828a3a1ae27
- request
- 435a3fc87d0c46bc6db30b0f6963c5836416f94c0db2a9444f344a1671873cdd
- transaction
- dabb161d31886542df711a2e8fca787ec421e469584899ea515f40eaa78b487ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18868
the chainentry 18868
- sealed to the entry before
- d69bfc29bc4b871ece30ce7c96e51d78ece8076c9860b891e5d640ca3e347fbe
- this leaf
- c7f82036eaa28ad5916a074ac95084f11908d54f7f19c49de3d60cae370d8fb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o2/8uqij5Y4mWbQqXxsOJjHjWbl0DR6GbVXWl2QkiLcU0wn2QgC32Pbk+ZvpNquu8k3OpuP50mpOrhbBILqiAA==