why2 reasons
mandatedestination_not_allowed
op 0 pays GBCMUQIWFU3VFEA3RPXSKD7SXHQBJFFVLXZQBJCSQ2R36IZQ6IKW5XWB, which is not in the allowlist
counterpartycounterparty_denied
GBCMUQIWFU3VFEA3RPXSKD7SXHQBJFFVLXZQBJCSQ2R36IZQ6IKW5XWB 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
- f87314fc199f0ddd6d8bea6000c2617f10d9fba4a3ea3f4569581842cc19e2ce
- request
- 15dec9078acd06c3bca3600586b0dea4d8ee6512986d12a471f95b734192658b
- transaction
- 277981b38d83c533e78ca7fbd328e2224e625601531fced587b3578b04accc0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16118
the chainentry 16118
- sealed to the entry before
- 6f021d60729e53db72167a99fe34817ef4b524a81fbb76db85b6d9bad09a77b1
- this leaf
- a20b5d9a5798d0007df66281a37119e081338f4e11ee23c7c5ba454352d22e9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iORlk8nmI0Cg1o6pbIgjFU51f8irTiQ80WM/y+dwwMNu6EseXQejf8dyn65+bim0AVMrYmUC4oF3Yf/oIBLDCw==