why2 reasons
mandatedestination_not_allowed
op 0 pays GDNDUZNBY7AZNTL4DVOEPAMJWEVWUWZYSXJYFM7NVU7BICRACI2AC3BI, which is not in the allowlist
counterpartycounterparty_denied
GDNDUZNBY7AZNTL4DVOEPAMJWEVWUWZYSXJYFM7NVU7BICRACI2AC3BI 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
- b0d905db91b0b48f55639304dcdabb1e796be2c28847d513ab110ce6250124ef
- request
- d934c9820aae6e734de153b5d3f40b73e14f58587224e9dbff75e7da7215c7b3
- transaction
- be4012919868509e453f36b88287c28210cf4c18900ad4294098648d9df1b4decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49536
the chainentry 49536
- sealed to the entry before
- 736dcea55a5aa0d5903291a37616fe46238315056b0f12deae72943781077c84
- this leaf
- 05e0566893fdcc47d52a3180ee8531e0a07497110f5b08ceeb1e0dd0f985c1b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ueQ43j0NmXAXjlrNRob3CdSCisspZT91yB2RzMrZcY9wssCi34uaavjEcytHVLruatczliqGfrpTdIA12abtCA==