why2 reasons
mandatedestination_not_allowed
op 0 pays GDAGZPN44SDPAEM3ZWB5MKN2ZILIDXU4X4IBKRWKPRCPCTDGKQ6W3Y7W, which is not in the allowlist
counterpartycounterparty_denied
GDAGZPN44SDPAEM3ZWB5MKN2ZILIDXU4X4IBKRWKPRCPCTDGKQ6W3Y7W 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
- 93cd697f9aa2c17d768fb364e626968f687423e54262e1ca84c874fd79e6850b
- request
- 31fa63145ea8c77b203d4d9b44cbcf531d18a4baad49aac7cda9993f79a339bc
- transaction
- d54a5e784a1fdfd89a30cdc933691c37df0939fbc7ed9d76a1a2451f95348813computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50161
the chainentry 50161
- sealed to the entry before
- 78ffecd9dacd2b8486e7b487d5ab3bd6c406d6f8c6d0c6a95a84432d7a6cae57
- this leaf
- 78825da7ca27cea6f897fbec22cce0529661ed93b41e94ddd920eed89a35a93b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WR61/2TcHsr+21QKYc9kWKxlGk27/b8lMZ7N6eF2hKWZF77O44hDI50za6/E5KfS/53aKlsWxon8KMKsztBzBQ==