why2 reasons
mandatedestination_not_allowed
op 0 pays GDW5RTQEVRGFK6ZFZZLC6GQYQHZ5D2DQYHP2UARW4UHRMLE4XLISERFQ, which is not in the allowlist
counterpartycounterparty_denied
GDW5RTQEVRGFK6ZFZZLC6GQYQHZ5D2DQYHP2UARW4UHRMLE4XLISERFQ 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
- 8f7ec05dbbc0215ecd6abc2f020a56584a4bab4869c0933fd6ed4958d0e24eb8
- request
- 65a984de78b0c4e9c47e1b7245da56f05468a552658cfdf840f66b2db17bb340
- transaction
- ea73b6a76084a723e5abafede9427610bda4b6a780502be2127d3317685ffa4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44608
the chainentry 44608
- sealed to the entry before
- b63474311cb7115d9951fb78cf9c594741ae074f54074eb6563dd575642f9439
- this leaf
- 46f4df928a24921e4a7257948606bae8d01a2524160c6568a2aa3eaabd9647fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hl5Ne0nFmS3KLqArfXcR00o/tYOd71ETMuqwwR6d7eGqIsjoK+brxt1T8GtHeupy2LFfyoAkotIy6sAW3PyQCw==