why2 reasons
mandatedestination_not_allowed
op 0 pays GAEBGEWO23UN5QOS43BGNXDAACXEXRVV5JBUXKXOAUV6RYJEPDYXAB5B, which is not in the allowlist
counterpartycounterparty_denied
GAEBGEWO23UN5QOS43BGNXDAACXEXRVV5JBUXKXOAUV6RYJEPDYXAB5B 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
- 5c1d13ac4c78c010859e5173e09f5eea7ed165b0cbaf856980b1ae22dea4f075
- request
- 380471dbf8ca74a7bf8fb94385c094dff7d07ecc9dbad5826d4e8f3ff4d53564
- transaction
- 1bdf5aec16d5747f636125f0cb7e4a84a0bb8546698d26090a1cfc3b4ed22533computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 682
the chainentry 682
- sealed to the entry before
- da3cf9883d81de7f27851bfe48965cb1b2e54071737b0269db703597fd176a1e
- this leaf
- c45d1ecd99f3603f8bdccbfeee20c29aa8c83d88ca354f6e39db2c37bce72ba5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zjyxGuGe2fghoMS35JoHXLGzd11UeFo/IqgDJ2WaqDh6z4aSSPQs1Mkhxg1WieYDeK3OaruykE8PHu7uoALSCw==