why2 reasons
mandatedestination_not_allowed
op 0 pays GDIPK5WI2RRVXRHBT2KOIX5TQVHTI4Z76Z35CTD2IARLRYEZNZCMG6H3, which is not in the allowlist
counterpartycounterparty_denied
GDIPK5WI2RRVXRHBT2KOIX5TQVHTI4Z76Z35CTD2IARLRYEZNZCMG6H3 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
- 563bf1cc6e7bf65c28874ee43539aae029bf134e02c2d0969cbcfb48a58f5a0f
- request
- 7a8e9e6e06fef7604929c176fbef0015fed3f5f42a258a45c5b27a673d8aed02
- transaction
- b9b84a06cacc64b8561f876538d012c17260066701e112a6c8277710f77694dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29402
the chainentry 29402
- sealed to the entry before
- 4dbfc6738f73c1800ee8fb9e039496206ff4ff1ad527d1f4f2451f6e1a8dd670
- this leaf
- c34ba7c3c566c32446f1e8c315f2edd58cd77139d096ff028ebadc9865abfa21
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nvOwSavo7w8bBtPLLXq60TtCrCRJp4BWvxvCJ/lc0JG3rcOwIYl83WInBlg7fHnNvIkiavuacakpEPPWgAE8AQ==