why2 reasons
mandatedestination_not_allowed
op 0 pays GDRPMS4RY4IKSBKM7HSQB5MBLQDRIOTQBIM4FPERA2XDWFFIBR7OYQIC, which is not in the allowlist
counterpartycounterparty_denied
GDRPMS4RY4IKSBKM7HSQB5MBLQDRIOTQBIM4FPERA2XDWFFIBR7OYQIC 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
- b40e484e62d9d4c47e5aaea4c9c94d7f1d8facdf0cf2e2dbb6287b5e77b38e41
- request
- c0b743844f5af2a0b7227eb1a2717106d3d609d366f2e7e076862566fb6257c3
- transaction
- 3bf30e2b923d6f02e81aa065d96d9bd8587e709ac64ff84d90aebfdc8cc29fefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38844
the chainentry 38844
- sealed to the entry before
- 709b59f834655098c7603985715a36de0cd8c676c75a5b66d97aa596954ecf85
- this leaf
- 9d70b440ddd9879410a92080343a711b96a71d505725c2ca4ffebe888f6fee79
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OzR2w3j56+D2JRllJ45Nw0jAf30bOg4Rqz17ZS9YmZY9UGh5Qm2ExeOUDGbrE5+6wVITvkkY6GgjPWVBU5fMAg==