why2 reasons
mandatedestination_not_allowed
op 0 pays GDNCDHHNAZW2UT4EZS3ISA4TC62M3ZWZL4HLDLNHTCTNYJZTHC5XHUWO, which is not in the allowlist
counterpartycounterparty_denied
GDNCDHHNAZW2UT4EZS3ISA4TC62M3ZWZL4HLDLNHTCTNYJZTHC5XHUWO 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
- 5a7030ba8337551a59df8e318792467709f4526ff906824d368f466430c52459
- request
- 86eb09bc1e6b86a31bb9d5ee1ca8aef87cc44c3cd28bead86bf9b1a2be003999
- transaction
- 2a56c24e12956a6e196cf6cb01a60669b2ef851a12660e0995d3cb75eb9c7ab1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50832
the chainentry 50832
- sealed to the entry before
- 50fe951d45d669945ef3795d0e00adf0099cfe6ebc997037b5447e981aa3919a
- this leaf
- e5fea96a76111e856f836148911e327653137e539d359cba4a0886bbb40ec2b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +GmsE4JN0tf6nj2yti/PodfdvKf+ABIMlg3dZLW4vjSAPjuzUfUFt8Qi9a/FW7ZR1bAkuZKAkIhb/ajQIwfBDg==