why2 reasons
mandatedestination_not_allowed
op 0 pays GD5ABHEKRMNDFWOKTJCDT2E4VTDMSICTSDCVSVAI7X7TFMYGDEXTGAVL, which is not in the allowlist
counterpartycounterparty_denied
GD5ABHEKRMNDFWOKTJCDT2E4VTDMSICTSDCVSVAI7X7TFMYGDEXTGAVL 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
- 98d3f4c73da2008d106c82e646ee30d470661e382f2ba3c6a9a334e725d5dde2
- request
- 5f6850f5b34ec21b595c7ee460af8d6f6ba919f464509adb743f1091646f3dff
- transaction
- f7f24daaf3a6e01af1dd33500278baa4e1e4abc093735d5592e0d409f6adcae0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26590
the chainentry 26590
- sealed to the entry before
- 69b18d0f4886d8c3b5e9b02d15a8661759ef7b6ba2d08f56dd33cc812d8c0233
- this leaf
- 4936f30c1d60f65ee09b254f5c7632beec08c85a0ae4471070cb09330db1110b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pFo23MzXxekkHGdUzLI82DcE1p/oH1sqhm2zWf+WUp2GcTon/Cr2mEeudS+mohKkLvSaXMZ39wbZ2XiDZNmnDg==