why2 reasons
mandatedestination_not_allowed
op 0 pays GBRZHGIZSPVXNFBNF4KRZME44IBORQP7WKRTC3K6HP3E647IIWL4AZEH, which is not in the allowlist
counterpartycounterparty_denied
GBRZHGIZSPVXNFBNF4KRZME44IBORQP7WKRTC3K6HP3E647IIWL4AZEH 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
- 8e74b8c1c1b5e56e7c3dd44cc76151f5117fde208e949fcaa9395952ad7b56c3
- request
- a1ed56806ddb09d319cd868cbd8f9f5d61c48098c7486b7dd5952950ed03feac
- transaction
- 6fe7e13cbec33f747e1c3a212b01b45b4305ba27313ff88dc739ddb33672e8aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75210
the chainentry 75210
- sealed to the entry before
- 55a5a2699b071bc22ce1f9addc94de843fbc97e8a80382410269ab432cfee4b2
- this leaf
- f5a747dd6dd01612ace1eff6b75557989ddcf4f1e004f8d0fb878f556651c073
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JrNU15XBmVcSOdZRHs4358gsoKWX1gCOyNvw62+iCPIqUSbIMSZqT7CdeuKGUMDXJlUto25CWChTHbRyoF+lCw==