why2 reasons
mandatedestination_not_allowed
op 0 pays GDK2TOPM62K3WVTHQEU2H7TETY53OTAKXOKHP65RULMM34E3GHMOCTTY, which is not in the allowlist
counterpartycounterparty_denied
GDK2TOPM62K3WVTHQEU2H7TETY53OTAKXOKHP65RULMM34E3GHMOCTTY 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
- b1c823221874723370c87c49f3e3e16930fb825c458ae075350f28d6c70ee5f7
- request
- 7a8c51bf69d0b36c54711f49079415ddc3c0027871c66f261ba2a254f696fdd1
- transaction
- 0aacbec5f021a8490d64dfc63ce49bb930fe94f0c8b5c3f9e97cc5daa4eee045computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 989
the chainentry 989
- sealed to the entry before
- e47287e74cde32b5e8620dea517bb9340fe4950f9d290460ffc72d1cf8782ec9
- this leaf
- f83cd590d3826aba328e30ea177f49362f810d7463a3108d171bf04547b111be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /sqDr0P5uO32vforuGjLBbWGPU7M62YtYjZKchcIG9tNNSwF+LPkoOzIckRqPc63UarvnEWAJYz3W5VThi7KBg==