why2 reasons
mandatedestination_not_allowed
op 0 pays GBV4KZQQR4R5I62MXVQPA4GW7GTIN4IJFMMOLHVSQGX4XEIYSGPS3TXX, which is not in the allowlist
counterpartycounterparty_denied
GBV4KZQQR4R5I62MXVQPA4GW7GTIN4IJFMMOLHVSQGX4XEIYSGPS3TXX 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
- 9c1c55fd6c75b0f9befbc08c9e7f1bad2a29dfdaf044fba0a3f39bbb98d07dce
- request
- fe77a94b243c0aada0ce89dbe3eccb5ffb0c78088936449547647e9ab7f971c4
- transaction
- 1f94fe2d818d447f3c837c5ac1807749ffa625125a21e73ce1a417cb79cf9e34computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24908
the chainentry 24908
- sealed to the entry before
- 9ea60c242a27245795f98ce566c07fedb7f56c8cca6049541f90ced2e3d58987
- this leaf
- 1ceb3b20fa59fc7df3eb9cb3a67dae8b9b0ab4192e795688b60d425219961ed3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kXsnZpAOBRZjoJ3I+yCVktUqvMgaicvqFZpmYlPtiFAgP91yT5RmMTZQtwtEagAU/y6bTaXzx5y1juIeb+yBBw==