why2 reasons
mandatedestination_not_allowed
op 0 pays GD4YXYELZ7JLRZBKJZ2GW46EKUGDZVFQ4LSNMRGKOG35KHWMC6WSK44Y, which is not in the allowlist
counterpartycounterparty_denied
GD4YXYELZ7JLRZBKJZ2GW46EKUGDZVFQ4LSNMRGKOG35KHWMC6WSK44Y 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
- 3675c2a4ac06466a725a8b6fa9c34476ad4ede9e7c6313f1cef83fa78db12c15
- request
- eb271f363614ee7ca44955868b93393665ec859a809087016bf0c554c3cd7c20
- transaction
- c250968094a16015511e03c560d36c6f574e0c4fedea9c9df95aa18bf459dfcdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32028
the chainentry 32028
- sealed to the entry before
- 88ca90c07022974113f380903b8b74f716a9e23cc06cf4fbf12e0f6516786ae3
- this leaf
- 4d56fb3e4c2c03312d72ed6215f392b475a6e91d072b84ab7d9bd3edd2bb38d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 54vr+/LTXMr+CpLc6NqA8jpVetrgm7zegeAM0HZcqyYER2pZUytZE2V7Rv3VqRYNqkJIEi8y2cXs6lnDFIO5Cg==