why2 reasons
mandatedestination_not_allowed
op 0 pays GDNMAHFWSXLOVDR25MBCUUBHC4J5GM4UGQBFVFEBBJYKRXXCY6L3AEHY, which is not in the allowlist
counterpartycounterparty_denied
GDNMAHFWSXLOVDR25MBCUUBHC4J5GM4UGQBFVFEBBJYKRXXCY6L3AEHY 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
- 852bf17b88455d5f236d49987694fff90da081dc8f98ec54bfc4fa4c1cd346dc
- request
- fc5978f0b92356b101be77439d460371cd0153b9181fd0021382cc50bbc5ff6e
- transaction
- 2645c21a62f205f98ac9e24a3cf7f21e758674cee4730ea5de44a8e12e925f70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74695
the chainentry 74695
- sealed to the entry before
- 4f83b1853c83fde51612a352db7189c00041aff5be286294c5517fe1ebea167e
- this leaf
- 14069feb3758b42ac6b9734bfdb4f75642f4bc407e0607592babad50520cae40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PSvSzEB5D82/1yIU5Pqg1JY2b7nKaCgWhsRsEvFsk2TzAMz+f8Jioyx765T/q10cd3J6bJQOdAFwefKGsXypBQ==