why2 reasons
mandatedestination_not_allowed
op 0 pays GBM7CG6E7ZQUSQ5YJSTXYG4KCJFBW3LXMCU43LPHNSKTAUEVWRJSG4JY, which is not in the allowlist
counterpartycounterparty_denied
GBM7CG6E7ZQUSQ5YJSTXYG4KCJFBW3LXMCU43LPHNSKTAUEVWRJSG4JY 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
- 81e12fab4d404f57224a5a4c0426cfc197002b70ee35b81e18e7a498799f622b
- request
- ec29040ae19d1fd310cd1c4045b0ce3b37e5d5f4e46686e763c5eb1e381a9942
- transaction
- 20645c593e9ba31a996a2c872679b2178ad6e5b9778ddb5734fd9ea8c747b145computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26459
the chainentry 26459
- sealed to the entry before
- cb2a2f2eec3b3d836c0b3527351787a67c57add46bbf5343bb502834773152fa
- this leaf
- 7f1b6a483b5ddea384f1b0ce80cba48a4651703f9abdc7514a7ef0f5895e0f12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kTFQRHmgZmec1HKsqv1ChgvK9dWA03owaatS/tupSAwUizd8fS4G8ntkfLHF+4jPpdRVICSk84OXgGDVjfMuBQ==