why2 reasons
mandatedestination_not_allowed
op 0 pays GBUQGLG5DEUYWRMUFMONIF6V43E52I3WDRGD5N3YFVLU64XMNOULMSZD, which is not in the allowlist
counterpartycounterparty_denied
GBUQGLG5DEUYWRMUFMONIF6V43E52I3WDRGD5N3YFVLU64XMNOULMSZD 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
- 2d7818a9f4dd594fdfc007795e32d9b4b6e188e8f47a05aaac9d27dc37c3ef9f
- request
- a4b41a63d753f7459a9b4783d19f753fef2d3c8d7da249b72f700c8c23e9943d
- transaction
- 8246c28bce94740b37c61897f5476dfb897477d88c1869541d652a63111f90eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9332
the chainentry 9332
- sealed to the entry before
- 4ff9bc33f05165672eaf436b3aab1e297dfca539410bbe69815947667165f926
- this leaf
- fb19051bd19dc12a5fbb021dc5b25a23be45142d03c92c6f5107a416434a0217
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NKs1rJ/fliImqjCD+GEOnTdqAH2wiJ4YwhrD+8CL48FCRTORwbAT2B0qfatbG35O9+rSu4hwAx3mPKLLMignDw==