why2 reasons
mandatedestination_not_allowed
op 0 pays GDVM5IMRKH6FHHJ7YR6XXYNP3P45WM7VY5YZ3RKDKY5TICMIDJYHOO4X, which is not in the allowlist
counterpartycounterparty_denied
GDVM5IMRKH6FHHJ7YR6XXYNP3P45WM7VY5YZ3RKDKY5TICMIDJYHOO4X 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
- 58a21a81b2123a1a0f866638fd37f0f9cb6eceb80e75037b2ce84ba8d917660f
- request
- 27130595ab8935d367249a96339a21a84f0558bf42c6b9cf3596018d5da50d88
- transaction
- 5faa770af68939e382df49a7629c67e05f69fbddbcc08d86f8abae750cc9353bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51726
the chainentry 51726
- sealed to the entry before
- 6a8a7a2ce1b7b66af04dd68e86ffef769afc2c14a70a8bb12b315509f60de8af
- this leaf
- 1bc991758826adab191dd5278dd85c35659424b9f61e41061a42b18072029fbd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DcDtYSKM02QTBQa3YLbbzsyp3T8AkNscChB0STWE7J5C3ooRw9EfPU25HkMt9ih2QRWCGExCHHExBcmc/6klBA==