why2 reasons
mandatedestination_not_allowed
op 0 pays GB4MUSHT5C6VVSYNYUPGZP5VCVD427P5BGEIGPFEPLSEVAK3TIK7YQNB, which is not in the allowlist
counterpartycounterparty_denied
GB4MUSHT5C6VVSYNYUPGZP5VCVD427P5BGEIGPFEPLSEVAK3TIK7YQNB 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
- 20bae06540a81c3de41334486528f8fedbad47816470d497902feb78d000ead3
- request
- 8cc0cfd5acbaed8ee2b686eae424c1fb8d413a2112e02cc0bb6a733252758a60
- transaction
- 675f18c8fada026bbee34846c05ce9fbc066db07a4979fb5ce6e258f389d77cbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77017
the chainentry 77017
- sealed to the entry before
- f4ac4cc383870bc1fc2ed19261021a5f84349b92d7e9d159a0ce0611311c0d4f
- this leaf
- 695fd5b52fd9ec806f1a24083f07de33ef075e9a65566fa6a5e049a612be59a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CagsnOWUxB1Kz7z7tLn1mYToieZFhrEq06iYCiN//q/wv4ykZYe+hVV/S335qVbhxagE+0Vpf0iq5oxa62jBBA==