why2 reasons
mandatedestination_not_allowed
op 0 pays GD2LOQFUVEIS3J4NQIK4TNZAA6GTPM5ORK7BSZVNOYZKT3AJOY3O7BOG, which is not in the allowlist
counterpartycounterparty_denied
GD2LOQFUVEIS3J4NQIK4TNZAA6GTPM5ORK7BSZVNOYZKT3AJOY3O7BOG 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
- c6b9be46aa61767bdb17998172dcf3938b20be1e7b8c2438a31026ce1376fe27
- request
- c948daef564d574f30dc8b53c36f1bf98c3940d62a65af9092a50f6f092cfb82
- transaction
- 3722b50d6985b87a65276dc0c3e4055777539dc768619c20d3ca335e5b8512dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41699
the chainentry 41699
- sealed to the entry before
- 4eac5066e7f47850519f8ba9a00f41c3f160c64b7fc4d892c3159367c378f14f
- this leaf
- e2a73befae50dad894e7e92c83f9516f7bd9188127e7baff5ec554719a900440
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 77RCsWRZmpHlK33ANsUtu2FdbxII06nz4mq8H2IvRMbzraQ5jwh1QntGsEo5FEJALEfipF/PHkP8S8Yxtk5lAQ==