why2 reasons
mandatedestination_not_allowed
op 0 pays GD6EOL6TBYFTAAUB7CWKY5L6ZL7OMX4JZDXAAIAGLLZ2I4UUDQYMXYZS, which is not in the allowlist
counterpartycounterparty_denied
GD6EOL6TBYFTAAUB7CWKY5L6ZL7OMX4JZDXAAIAGLLZ2I4UUDQYMXYZS 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
- d579c5b72d3661d86d141b9a1bf4290daf60aee797c55d391c916c4b49f21112
- request
- 10bafb070d1e9c06cbc2d8793cd468739807c1d4ffa0beff82e8d01657d421da
- transaction
- f8d12b3e214b6688484ef672bf32adcbf3778acdccb3c8eaeca804d726e7cffecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60620
the chainentry 60620
- sealed to the entry before
- 28e0ac5e1e261b4f8d988243e05b641f60c70655c3b5600613253c90216fb152
- this leaf
- da3c64d125dd77bcf4402a186f27845139479b63601af8238efe07fc88804032
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h1J+Ken3UbR7i+xTClW6Iq64sQBpKC71qjl+frK2eazAvw0qW8kVXEleqRIS6p16a2CyE7UgDDGeVzCJ4DFmCg==