why2 reasons
mandatedestination_not_allowed
op 0 pays GDCFOAGNZVAXQGTBMM7R5VK3MJ5S3UK2ARYX3ACATFSYT2W76BDWKJZS, which is not in the allowlist
counterpartycounterparty_denied
GDCFOAGNZVAXQGTBMM7R5VK3MJ5S3UK2ARYX3ACATFSYT2W76BDWKJZS 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
- b34fd01a00c7ea6c0eafaa9834201827b315cf972ea4ab14f51dc8961d9ca84c
- request
- c8396e15832d936e4312073b432841b5f533fade9a32aadccdb582776638b7bd
- transaction
- 6bf0990848993ad62a679b05a357cff93f86b5755e8af1bda6930a5d6a8b0e19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1716
the chainentry 1716
- sealed to the entry before
- 67c75858f5484c14d50f6656137906c2e9ee1b6c935dbe8b0d79b84ed200f3e9
- this leaf
- 3d5962fdf010eb88668b7d1a8f4af9cd7916dd9eeecec18db038a66db8d3a76d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SmatJ24DH/nqfCNLvqP8yXncorPa3UAwcN+GiJzqKN0Hrortp7UmdAfF5TBjbaitmb8ic8kb1vZEmNLHaLYfAg==