why2 reasons
mandatedestination_not_allowed
op 0 pays GBKMPSYE4B3MJX5O4PMJAOT2GREHOHJ5YONREVZXKR3NS5B7X3N6UE2A, which is not in the allowlist
counterpartycounterparty_denied
GBKMPSYE4B3MJX5O4PMJAOT2GREHOHJ5YONREVZXKR3NS5B7X3N6UE2A 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
- a5878d9550d57e19830461a2009e226b91c0656536068bd4869bec800412130d
- request
- 18bb6f64ed9ed98f1d85a61012bd5ddccfd68eca61adfd18ae5056f923b8882e
- transaction
- 471fa9b3450ea10aa572a45af8d66697e880cd8d7bf1bff1690f91011ea5bccecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30582
the chainentry 30582
- sealed to the entry before
- 5830011c96b19e1576163af2ab7e4367bc8ee2df73067d3b3cd9e7d08cc9df52
- this leaf
- 6859ad3ce16f86152902ca04705a00eaed6915ee886ae158f3b7aa6001f46743
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 31vc8itDhDW6gdVWA6JI7l5ONCzmMKkoJkRYOR/2HRB+7SvzVxyHmUtsaFowXEoLsuVaj6/Y3qti8yrFK4rQDQ==