why2 reasons
mandatedestination_not_allowed
op 0 pays GD2UB5253N2YKGUS32T7B7OKDAI67SHN5ZREI22NFXRR7T5CEUJ27J3O, which is not in the allowlist
counterpartycounterparty_denied
GD2UB5253N2YKGUS32T7B7OKDAI67SHN5ZREI22NFXRR7T5CEUJ27J3O 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
- 560f3f3318dd343238916f9e664e8c249367a07a96e157b6c6e3f5d4d65c154b
- request
- cee615da03f1281279a149dd0da0ca4ff00d7c1b4d743979282aef287a9f1ff9
- transaction
- 6c1086e2cd6ee7516fdaf3091faffa8d760781e0561505ac609c61c210828d8ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61555
the chainentry 61555
- sealed to the entry before
- 5dedcbfa06b704d2f071275ee51ce799930475c0c2f0bbcf052bfdb2b9649711
- this leaf
- 666e863f3347870cc0ce733d4d501193549b3cf4ae16c93a5401f63e2594103e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8lC9eEbcjbrg/PXoj2DFZ4LsscBpiO36lcxxxYRaDE5g6xKpBxOaUjamcnPpm6NmKpkvUSuY6VCAr109dw4aDQ==