why2 reasons
mandatedestination_not_allowed
op 0 pays GDCUIVILNE3GKFHILRGZ4RYT5XVY3GTFJP4JUY3ZISJUK6NF7LEB3FGO, which is not in the allowlist
counterpartycounterparty_denied
GDCUIVILNE3GKFHILRGZ4RYT5XVY3GTFJP4JUY3ZISJUK6NF7LEB3FGO 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
- ab0ae0beff3dd5827dd6c130e1bbcecc0942069de89ab5eb1407203e3921e662
- request
- 90dc9a7ec1a81d93f1cd804eded6fa122de7ae79f3fc3b68b25facd1a73b4fdf
- transaction
- 27ce0ef63608a095df114106e79d9cf9946fb9067ccd00ad905cac79e40c8ce0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22100
the chainentry 22100
- sealed to the entry before
- 6253e0f82170ebd72eda3eccb45e116b7220ceabd3dd0dffd259d5a97412677b
- this leaf
- 409680fe55ee604d0ed63421996998bcfd845bf59d230357ae15264ea7124256
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iBGCCobpiBwIUtyRD1ix1RIt9DuyFrzUGAPyR9K4DO4smGDLlluFHkJ6i7p/twp/+iJpmEp6MVQtMQEATEe1CQ==