why2 reasons
mandatedestination_not_allowed
op 0 pays GDNYUAR2FVSJJGDMXWARLPRINVFG2DF64XCTTQNWYGFHYLJOZVTU5AC2, which is not in the allowlist
counterpartycounterparty_denied
GDNYUAR2FVSJJGDMXWARLPRINVFG2DF64XCTTQNWYGFHYLJOZVTU5AC2 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
- 53bf38b62d27c83ff545d6ab0636cc91ef65d46055bf943989aa55bd794aad0f
- request
- 27e38e9d0be99a153bb30b4ef53e94a019ea62a53cdd9a4b21a96510c6e89939
- transaction
- ed9c6cbf483b5f6139d56a08ea3fdc73b5d94014151c1822d2b0e48a15f3cd3bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65850
the chainentry 65850
- sealed to the entry before
- 8b64b1bdaafe4fa8448bdb807b55b14f43a4daceff29a50c8b997557f8ea1343
- this leaf
- 4654c9bd5b623ceec9db57b25c2d0d3d14247398c57610c2ec29a4cd4dce2c8f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dnWqIcWdoDdgxur2KMN+NSlN1bxegKfaA8ItiGt46ojZKbL8d6VVkO4WT4BTCoJX9CcOdoZN5AR8jW2czsGlDA==