why2 reasons
mandatedestination_not_allowed
op 0 pays GDSF46PUJ5ME6EHGXX2W75ZYESZ5YPTFDWS2727NY3L366A4RVMEKGER, which is not in the allowlist
counterpartycounterparty_denied
GDSF46PUJ5ME6EHGXX2W75ZYESZ5YPTFDWS2727NY3L366A4RVMEKGER 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
- 4e3e064386bcfb2607bff299c2d789305c6bb67215cc0d1023aa10c633ed4ac7
- request
- aa073d6e27d273cf8c77ba0150b320df38f8dbb5a2ff1a16a46d09c5faaa9ea7
- transaction
- ddde641d70f4fcd7177f8a52172fc6c9f269e48f4d0aa416968bba754591aacecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23135
the chainentry 23135
- sealed to the entry before
- 060c443500619a3dd2f1305662938ee0d90e1a02aee5d45e1e141bfbf33a7e03
- this leaf
- 6b77e2d379c78d80f7924f3d05413b378b9f609f861e0c90927c11f3ba26ab8e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +Zug5kCHY20f22s81W7eu4WSf/+kcdddGOnIlyHGwCVWtGQQxRbYV0z+foNjquc2mBnpxGqrpX0UX2BCHqh2Dw==