why2 reasons
mandatedestination_not_allowed
op 0 pays GD3ISCHGW5CBKVPKM3O3CVKVJWQ5T3P5SNWU27ILNLZDJBTFJGJMPXZM, which is not in the allowlist
counterpartycounterparty_denied
GD3ISCHGW5CBKVPKM3O3CVKVJWQ5T3P5SNWU27ILNLZDJBTFJGJMPXZM 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
- 32684f61e0d45974f1ac5eacead3e73192b897a2b1c62cb666ef93c6b61adeb5
- request
- 461ccd5ed5b77975d45326ac729e4fe0c5848575621710a7b95a8fc0dc9b335e
- transaction
- 45fbc9230bb4c5a3dc0bb90c8d300cc7fea093eefe35570c32a92b75aa299e7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68225
the chainentry 68225
- sealed to the entry before
- 255745ea4857ed5b61c88b0bb4b5ece482e36814a583eb2016f9f34291754b0c
- this leaf
- 1ff3b35eeae263fe00ddbade73d73fa77931fa81ddee022759f1638ce10db90c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BbnkBqhhzdXmvFi8sQaqx2Tc4swdDYzOS1m+5KFZem5nXt6DOXqT4HKVYUgxLI2izgFn4lpr3MCZAKKcqAh6DA==