why2 reasons
mandatedestination_not_allowed
op 0 pays GDR4R3LRGWPFUXNSZ4DN5ZZMZO3BBVZCHQV5V4S6JCR7AAPZKSRTXO3A, which is not in the allowlist
counterpartycounterparty_denied
GDR4R3LRGWPFUXNSZ4DN5ZZMZO3BBVZCHQV5V4S6JCR7AAPZKSRTXO3A 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
- 8edbee6ebe340276dcb699b097320078cdfb5da04dfb302f0561f6b0320f8e04
- request
- a59a0971398f9bbfcedca8696ca34a94d4a9e2b98a446b1c2a37d8c8d7a20f88
- transaction
- 2a951509ccab0ced8d6e17300819d0f366194d9d1ec11aeaeb69d4a7246a541fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42281
the chainentry 42281
- sealed to the entry before
- ceef029bf13696fffe2fddb5ac184bbb17e2c2a2b99d0838a4de9998dab9f4a5
- this leaf
- f0845f3403516f1dc791db396dc15f1aa009384cd61063f958a8763b9f11450a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uBRr8maHGJKVs3pBXNMw8UgFnQRWknWEpnpnrJNA+psrG5jsE4VrFDkvIRNwZn+cAxGO7IwzyAPRCStOwWROAw==