why2 reasons
mandatedestination_not_allowed
op 0 pays GBSO6S2YYW3UEVNDATFQE4YCRUEW7SQ4UOHUNVVUQYQ7JPVWTX5NWARR, which is not in the allowlist
counterpartycounterparty_denied
GBSO6S2YYW3UEVNDATFQE4YCRUEW7SQ4UOHUNVVUQYQ7JPVWTX5NWARR 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
- bd0e55846a3299e5a6ab0348c223c92ac85ac4f7505fc7f45876e2bbb89cf52e
- request
- d87d81b4bddb7355d63fb5c0839325f4bbf7470359212837503903d6406c4322
- transaction
- c377691137decef08285bfc887fc6f7af32685043263d44909dd36fafd755a3dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49118
the chainentry 49118
- sealed to the entry before
- c884a5d26af6548ad11465201fc0b310517d818559e70c911e8d3779e09e5935
- this leaf
- 43e4bd473e3f6ed9bb504ab0f35914a1ab1ebc7c5053106a987292076343ffbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BJPiCePL/8FgJwDS6EyKdZG35bQSChMRCeksqIwA0Dd7UjZl0wHzNcUevDY0yfvwLfIWBtxDzCWuQ0sQJSScAw==