why2 reasons
mandatedestination_not_allowed
op 0 pays GDSZU5XV7O4X6YQDKQLBZUAUQYG3GZRYL2FO5GYJWNMJLWG3UBEAOVB3, which is not in the allowlist
counterpartycounterparty_denied
GDSZU5XV7O4X6YQDKQLBZUAUQYG3GZRYL2FO5GYJWNMJLWG3UBEAOVB3 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
- eb475c68f22c3ecc1b0c9e725a8c8d0463d325c92eb208a0408431a3607b4214
- request
- 1ae62119eb3732748f464b49504e0bc71730ab6c8515a62b4367b8ff61e3ea4b
- transaction
- 1c81043e30ac3ba4ae310861dedcc56101ba8e75f78fda57b8a764c1fe61dc9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66624
the chainentry 66624
- sealed to the entry before
- 690ea4dbfa5cfd061847d07b1b5be7713ab777ef6f7b472fdbf9e1661e847060
- this leaf
- 28932e397224e2e66df31fb1379d31008b3830a663a6b3be08059916f1c116a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ejvIyQ+utXRiC2R/oIIEMVov3HO5p9u98BV54lfBCnvU6qGM7u16hwsKEjQA6uS/3498W9cP655+3VU12oqTAw==