why2 reasons
mandatedestination_not_allowed
op 0 pays GDR4QXCDGSDG5RNYC6ZOWSEVRVUENBUDNSE533GHZ6YAYFU44NBBXPUT, which is not in the allowlist
counterpartycounterparty_denied
GDR4QXCDGSDG5RNYC6ZOWSEVRVUENBUDNSE533GHZ6YAYFU44NBBXPUT 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
- 222aaa6ff1549f6c96c610ab8407c9e1a06d9ac3aed856a07eed9e9cf6cc2788
- request
- 57cdace55e126b34e5440fb76baf6f2faf365621676eb073ebcb8de285212fd6
- transaction
- c9bc7e63487c5b237d3f1ddba0457600e5d58593b3868faf5c0d5beb9f256153computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28167
the chainentry 28167
- sealed to the entry before
- 77dbe7fd436f6978d04e61be64b52c212d2c0d645912a19ae31ac6c2df87460d
- this leaf
- 21e7af904275bcd38ce14de0cf1165cdedb76ef4b97c6e54e789a624b6fde28d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5eoUYKMX2YOJhQeCKbQ9J3MlX8cjS0gGFZXI2WJUnWfFf3VzkHsaB8EEKnZDv1gGGo5UxhBfH1klbKkvhyO9CA==