why2 reasons
mandatedestination_not_allowed
op 0 pays GDFL5T7YFQCRAIN4FENOP53L7RB3W2XMXBYTOVV2U2SULL4ESRC6IFZ5, which is not in the allowlist
counterpartycounterparty_denied
GDFL5T7YFQCRAIN4FENOP53L7RB3W2XMXBYTOVV2U2SULL4ESRC6IFZ5 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
- 709a85e18601f279e83ed43dce5be0a636de431b08b7804122e82f973d6e7868
- request
- fa9fb1516b56b6df18eb323e6afaafb02542250d4b0f1a41a806cd694f9a91aa
- transaction
- 5ec9583b726df3b92a6e8ff759e3b996d41f1fceb2051300f6ca5a5d9cee24a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61915
the chainentry 61915
- sealed to the entry before
- bc96a3f923b14b754d45d0301c7989386dbb6a3c74b110556c75e16535ad9000
- this leaf
- 308840df99707e313455cdca622c4f16a60743bc4d42d3bf6425ab94714979f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Spjsi1vM4l92lPw82dCjYwVh9Wtdc0M6VtPELT9Sl8z1rIX/+rGVSlieiXTxKi/0jwHZaw55jOcDevG3oGnCA==