why2 reasons
mandatedestination_not_allowed
op 0 pays GDPC4UDJIHL3UPSXCJBJLPX5RQAOVO6SG2SROC5FEUAU7O2JJQ2HFHIY, which is not in the allowlist
counterpartycounterparty_denied
GDPC4UDJIHL3UPSXCJBJLPX5RQAOVO6SG2SROC5FEUAU7O2JJQ2HFHIY 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
- 2790c5cd686d3f1ee6b20dc4f190139e516269cad02a4bbdcea60749960bce91
- request
- 706ad961c43ca00e1875c0288c6e3f05a02aad48b7124b2b85a3683ce6cf8759
- transaction
- f4245a6202b2f831f208cf6f8a86b92d6caf4ae1f4d6b5277f2eb4b5fce8c9afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68799
the chainentry 68799
- sealed to the entry before
- ba64a3eadeb3cce83bf67380573b00e9df9129fb2420b08a3f047366bf8850cb
- this leaf
- 869a1d5725b2008c34ae5da078d9ff65c9bcc75a5a1955fdacc708ec5176df17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qx8AUGLxxewzJ8ignZVqbqQw1ieL1yldS7xx0rb/A6FTW9lAEcsWnNYvmt1GSLXe1wI8uWVDYMlobcFhzTISCA==