why2 reasons
mandatedestination_not_allowed
op 0 pays GDQCOZJNTZLY3NCCW5IODODYB3ETGC3ZGKITXJDV4G5ESIGKNH32D23A, which is not in the allowlist
counterpartycounterparty_denied
GDQCOZJNTZLY3NCCW5IODODYB3ETGC3ZGKITXJDV4G5ESIGKNH32D23A 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
- 0600a90a94e6aeaf5ce9813c02da3a5c4b245d728727825d9bf7ceb5bbb55990
- request
- 071beeb8b2fecfba87e9a3648781ceb73502fec8b40ecc32820c16bfbc664c08
- transaction
- 2cebe3ade7bafb8648f791f6e203ea3c91b6bfd14bd02eb785990165132761f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 822
the chainentry 822
- sealed to the entry before
- fc0cc9d3e26f8f122ff6ec1e883784f08f66632422a6eb9b045d32aaa04a6989
- this leaf
- 780064cb5837060817dbf7461ac2fd9e79988ad79cecae981ecc6c93c6e74e40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VLpoUNeASZnLxqirLh1Qg9NFXY0SxVQuZ2rZMWvUcgzdDw7svd5rgKBi6okY90UIIH1HHXZ60tWjFOI+aKYyCQ==