why2 reasons
mandatedestination_not_allowed
op 0 pays GDYM4QECW56LFE3ZWD3NFZP7TSQLSEKXS7ZUNTNMWVKTXVILHQYKTDUJ, which is not in the allowlist
counterpartycounterparty_denied
GDYM4QECW56LFE3ZWD3NFZP7TSQLSEKXS7ZUNTNMWVKTXVILHQYKTDUJ 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
- 6bd57dd212d0107a5d516169f253d6e54169d0ac417941bc613582f9ac233003
- request
- 6036eb74e5be6f148d9b62f238dd775ff62bbd947d636d9c81690e174f758cfd
- transaction
- e98399af66fd58e93e1974561a53d483dcc32611df9f3eb9510a16dd59698589computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32048
the chainentry 32048
- sealed to the entry before
- ec4637ed897fbe18af1a7dc8984842e9e62392fad699e6654acea87023013eb5
- this leaf
- bbbbede928621f1e5c6b383292fad9b48ad2c5add2d680a9220a6d7dc1f5e4c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pF17GCPZaUNYYfyHFSK3JC1/l/SeAeMMWDAUGmoEk8BQRPOO2+yUFrpIZ617ojza1578gBw2FBK0FcKFRQC/DQ==