why2 reasons
mandatedestination_not_allowed
op 0 pays GDPNKUJABYEYUQIBSCVKKAXCZKMAMEOIIEIYJQU4MC5AMXAA7DNCLCXS, which is not in the allowlist
counterpartycounterparty_denied
GDPNKUJABYEYUQIBSCVKKAXCZKMAMEOIIEIYJQU4MC5AMXAA7DNCLCXS 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
- a21e42d17a3bd36de268c070f772dac2e71db6a83db5fd7c54e5ed3feb6b420e
- request
- 128c906f39e6f5b5644e3f714819359676039af7c6b0c321cea2e67edd52449a
- transaction
- 37a9d9b98ca639cb95a2adc68621eeb10db1c039c5ab3a378b6ef8808ed2172dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26665
the chainentry 26665
- sealed to the entry before
- e26749c46e535a272265dfeaddf38de30db5905a093cd50ccaa3452364794d44
- this leaf
- 6483197d5fc5893e69f7d50c0bbdf87aa3021319c2400d6c79c54af503938530
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D20v4RjOVcbkDD+VIT1TWma+vclIySKj2Ee2Mwc59420fPySQeah13KFFid1sYUmZwoYYvlzWtynbjjIgEGgDw==