why2 reasons
mandatedestination_not_allowed
op 0 pays GDIUXVIRCXMHCIMZ4TPOBYQMY2O3EB44Z65QZQBY37NPFFWXFFE4WPGM, which is not in the allowlist
counterpartycounterparty_denied
GDIUXVIRCXMHCIMZ4TPOBYQMY2O3EB44Z65QZQBY37NPFFWXFFE4WPGM 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
- f2fb16c7d871944f28fcd92af49b122ec2de1e19285ef0a2a20d6336ef2fd6c4
- request
- 451bfc62b4404e430a940641c5638f029a26a1107a0f3c2342e6fd37ddceba37
- transaction
- d06313481edac1cfea5dc6f03e65b993f85ce93280d64bfae96da2d1d973e16dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63586
the chainentry 63586
- sealed to the entry before
- b9ebcd4a62f1bc3c48017bf79195fa591c71927643d4a5fbf6c2f8d3786cfadd
- this leaf
- 1c4fef7d3cee6b014fc19d4e93c7da8bdd8cec727e071764c54a5ee4570835a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TIRCdcr9nTy2DCfXZ7IHrKIqyVt+D0JTjSG+Cz/Aw9cmg4XHvKjUogZrr9z7rmu1sN6uLmtVrNYsO5z+z3wkDA==