why2 reasons
mandatedestination_not_allowed
op 0 pays GDNBYW7W5D4Z2RJHZU5YJ5ESORNM3DXFEWIHZ6ZQVUWC4DECPMWSL4BK, which is not in the allowlist
counterpartycounterparty_denied
GDNBYW7W5D4Z2RJHZU5YJ5ESORNM3DXFEWIHZ6ZQVUWC4DECPMWSL4BK 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
- d8c5f192cc2135a0a5618d8f3c42555df3f02dafd2ef5fee8bef45a85999a86c
- request
- 0227698066028746a4b07926c0bcd3774e205eb7af5d7086caaa46670afd9f68
- transaction
- 74290bda408c7f0cd8d32640fdcbc3dfc9e884336076e28e68aa53b5be3f6740computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44109
the chainentry 44109
- sealed to the entry before
- 0339c369f41f8eb5c32cb1266c93f50eaa309765429cd76203c5e165fb81cc16
- this leaf
- 2a8f2929722e240e6e891d27d01492760fad9a957722d705be568fec1aaafb56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W6slaWxDohdFvy5z1S6f3cBkGLdA94GnrD2hvyKJ8RRb4fXlx0E8mhh8BIQj6GR2wrNWRQh//sh1/r7PJn+vAg==