why2 reasons
mandatedestination_not_allowed
op 0 pays GD7YAITMKZ6VMOF2QLOM55FHGCLX7EQ573JKLCPAOAKQ373U5KEIKKZ2, which is not in the allowlist
counterpartycounterparty_denied
GD7YAITMKZ6VMOF2QLOM55FHGCLX7EQ573JKLCPAOAKQ373U5KEIKKZ2 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
- bcd9cab11108da41208220a74e86dadd0a6ce55c32e61d235f967aad826b2f5a
- request
- 4d961a92911cd2746a95277f8a73c435109a73cc9e4c0e9b3b3b3ae3975bca0a
- transaction
- 68cace20353c3b27dd07b5d8fcad90e281331e728b1de4f690efe27812eadc16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76900
the chainentry 76900
- sealed to the entry before
- 693df4a3e4f59e24900a4f39839527be5559563dfe9467be7667a3b8b9372518
- this leaf
- c5e2522381ff9935df9d68d426dd4824ab894eb5ce56db8a173ccd616fae9a3b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Idn23pCa83YncUHrwNKv5gc6u8U+ia+edtk1lyUOALf8vtrBGC8djftTMA6YYmVOA/OtQfnLIdGHhBTQFMApAA==