why2 reasons
mandatedestination_not_allowed
op 0 pays GDTZCTZT22HFYTXDEBXM5QNNNLG26VPSSHXEGPWNDSMV4FXPKTVU4Y3P, which is not in the allowlist
counterpartycounterparty_denied
GDTZCTZT22HFYTXDEBXM5QNNNLG26VPSSHXEGPWNDSMV4FXPKTVU4Y3P 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
- b23931419ae2be7236724d42ce7dde95a6a2d3e2987e06d3c6a48b3f65c05030
- request
- d86028f86f3b1f1c6278391b854099ee513f53a4eb9849e80fb97d01db3a52e6
- transaction
- 1870d2117eecca77592b010a7075ed4c66b1de8871c0daecfe1ed83b1d6b6dd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30687
the chainentry 30687
- sealed to the entry before
- 65a8bf429e9ec46637146974fa364d90940310e15bbdbe5f2b8a4423e92589f5
- this leaf
- 63b9cd6fd98cbff7bca1025cdec4abc704b27794f0c6939a7be13ec5b2db3852
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h6zZRtGgr2bnQv2/DVoES/Yv28Q48qRQYln4cAfV+zKxooYVXMMknsED0Lb2HzCJ4dS0EFVux5AhtSgyR2AICg==