why2 reasons
mandatedestination_not_allowed
op 0 pays GD5AQQVR2AM6XU23KDCQUDZTZ3AM3YBVMKO3QZIOIJUW4YMXDJFAWKPN, which is not in the allowlist
counterpartycounterparty_denied
GD5AQQVR2AM6XU23KDCQUDZTZ3AM3YBVMKO3QZIOIJUW4YMXDJFAWKPN 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
- d479caa0962ff44c4db0b6d9b0f0bb72c15040eec45997f850a7c6c4b5a14c34
- request
- fe95efc2547c4b4457a363d3c1d889a33df64228b05062ab59cba4d223142fb7
- transaction
- a568309d42632506d9abb86f4144e2f1a5be971827f3b7dfab7d6ceecea17383computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76250
the chainentry 76250
- sealed to the entry before
- 72c7bd170c5ab0e3dff8bf7c3afeb4af74b6b80f6e63c0935f2b7360b357c542
- this leaf
- 13b522f74e3c636187b78e565f8798c6191dbe33d28f03b5e30c36ec738c9117
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uDFdCFrfDwBzyC30+UBdsHdGeXiCOvAayVjgFjLfoGfZWD9LYtpMa8Lu8oUxAqfymo4bWNtTT9DtxXZ2sBPoAw==