why2 reasons
mandatedestination_not_allowed
op 0 pays GDIUMJIMGSJASKXZTU3OYIFI2VCPLEJKXBO4R2IBGIDKFKBRWG7ALJO5, which is not in the allowlist
counterpartycounterparty_denied
GDIUMJIMGSJASKXZTU3OYIFI2VCPLEJKXBO4R2IBGIDKFKBRWG7ALJO5 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
- 7dd43439f3dc271ee20fe84d2aac21df0c21fea6a63aaa9eec0984b6aa4bf67e
- request
- b40a4dcfab0a10873f2979b8aac527f6e4f064f3b43b9f668d5b11c54dbdc9e0
- transaction
- 4489bb8530d1cb4099ef5d5bd78fb2063f80b55576077b600c1b7d55d489ee92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17244
the chainentry 17244
- sealed to the entry before
- b8b5f80d809f387834eb2b06388ba00a628043b9413fdfb18b70c92b9bd8af70
- this leaf
- daeda4e064a6b79c96f226ad255626531ac573ddcfa77616efaaae6129bbd297
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vmJGLdQcqcaNFoaNex1rBQ4539yPBJ2KxRh7QmN9dSH9gAebe+t1rsg8D7xDFREWwusfjbqLIAykuYqxbrffCw==