why2 reasons
mandatedestination_not_allowed
op 0 pays GDDHKTQ4SLB7Q22DKCAJ5TTOEWTTTBOH2VBIQXG32EOZJUYNA3MGOR7K, which is not in the allowlist
counterpartycounterparty_denied
GDDHKTQ4SLB7Q22DKCAJ5TTOEWTTTBOH2VBIQXG32EOZJUYNA3MGOR7K 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
- c9cf14d9798b96c211cc5420da91a5be389c05e9d4186e86b44d127b6ba80e3f
- request
- bc90ede3bb11c5d357a2eac65084ed5325cb0d769dea00cc743da576abdbd9bc
- transaction
- 3b7ed39558771cd048aa8760501e10ff71bd79054421bcaaac4964681edcadb7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77088
the chainentry 77088
- sealed to the entry before
- 1e821f7f1107064667cca8108ad0b87ca9087314c7865b0d3f6fac2d5cd0083a
- this leaf
- f35935c2b6283e664cb83d1b5d8af9bb6516022d60e85e44789504e7a53dae8d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O0ezIe+STWRZpOoEBPvg+AMeufkZ6nPCmVnyLR3UqxRu/Cd9LalgTd+tQ1fggNsiqTBxHVYiHUQf5OjBM5JKCw==