why2 reasons
mandatedestination_not_allowed
op 0 pays GDBVX6F7AUEIIEC7R7MCK5ZD5NNGGBEXR3PRS3QKIDMI6UAPMV2GXL63, which is not in the allowlist
counterpartycounterparty_denied
GDBVX6F7AUEIIEC7R7MCK5ZD5NNGGBEXR3PRS3QKIDMI6UAPMV2GXL63 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
- 25b36224be06309b9826f01a7a6e2fe0971dd16422063b5862b70b92394a1dab
- request
- c79024a7aaa620beed13fc95bb07e30fe486f18f39e5134be649eaff8c4b5c69
- transaction
- 418d8a918a9b699a5dcd10c8d83c970222e7eedcd77d4545b7738abb7f519873computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56606
the chainentry 56606
- sealed to the entry before
- fd3d1485341896f2bb8040ed5eff91bc9f60d585c134e350c9f9d2575b3b9757
- this leaf
- 595c602b76f3c51dfbec4d3b39d2c5d5ad4578d520c3e8247fdfc61d70347203
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pKenKYGDzrbQCng5YcknHxENMiPpfLkX3PfQCbfMXLb4Z3rX2zJMiiKdBceXSJ/pvjpzYkms3eBDhD+KvN2ZBQ==