why2 reasons
mandatedestination_not_allowed
op 0 pays GD5DGIZMN62HY4Q5ZUY5TIF7Z7FWVGKHW5OAAALJHLQ5P275JPM6RGFY, which is not in the allowlist
counterpartycounterparty_denied
GD5DGIZMN62HY4Q5ZUY5TIF7Z7FWVGKHW5OAAALJHLQ5P275JPM6RGFY 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
- c7f27068213dceef393de4c5f67e2d038135048d5daf869b39cef8f71cb300d6
- request
- 4e5d7de3d9e2ebf0fd7b2e4cc192fbb2636e3321cb8a03f35a211120bf0a0ff8
- transaction
- 5c6cdf40de6a731b47d692c2810593c8f3dba832bf6f535ba578a3f48057785ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18303
the chainentry 18303
- sealed to the entry before
- 95e8c951ef37d10990c658fb2aee272a4bb51103013e98fc89b83af6a8fb236b
- this leaf
- 70de7f37c69338600cad8d79338a2b75c999c6a9f037e718909d3a290a8419ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xqTmRfEuaAseDwlZNMJt/FcMM3GWLwSBR/WKGZS/xBnm0ZXeFUVhnf37TrrtldoC3Tc0gX8t+mIAGvj3JtATDQ==