why2 reasons
mandatedestination_not_allowed
op 0 pays GDUJTHJVADVRKJHDFVZVZN5XJKKZZ4NRSBDUJC4A26V3NN6X4VFQANLX, which is not in the allowlist
counterpartycounterparty_denied
GDUJTHJVADVRKJHDFVZVZN5XJKKZZ4NRSBDUJC4A26V3NN6X4VFQANLX 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
- 34952ed983bce094853f31e81fc53e9dd51e71c241efd9ef6a012c6a0e482090
- request
- 85366e72372fdcc92d964188f00daf30d1e37c55e0fa70d62a0d1f841185049a
- transaction
- ade98d31cfbd146a40158a42df26701e4b14a65485b1090f35f0ce95de3fc9a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38633
the chainentry 38633
- sealed to the entry before
- e897ecce584c713e9424c1ed77875e5f9acc2bc7eed52034b65e44262e20a51d
- this leaf
- d219ee112cd97369e5efa275064292d9065fb3a9c317842c1fe91268b2992c56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sgw462QaidD7JPQo5TF/Tp6WRDioQHzAgtrD7/P+4ZqbB3BUnJi2TDOqZystD7nCAg+MglSxkZ4gqaoximdFDg==