why2 reasons
mandatedestination_not_allowed
op 0 pays GD5UDJCNLATQ3SRR6AMFB5NB4SA755ABBTBAMNDNPZX3QU57GLLT62KN, which is not in the allowlist
counterpartycounterparty_denied
GD5UDJCNLATQ3SRR6AMFB5NB4SA755ABBTBAMNDNPZX3QU57GLLT62KN 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
- 7a731a33a23ab4a712ae12fa34e0c2631112a56bc4d8eedcee8711ca0517a28c
- request
- 329e076b16a235e967740464e7cffe1e1c1371b57cd86a52f96232dd19b886db
- transaction
- 78907b1e8faeff096eb153c8780076dad167dac3cf89e929b3cd6160a03e6b2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51970
the chainentry 51970
- sealed to the entry before
- 0209ab0e23f80ecd674560f685975e0043129b657349a4183e502ede5574f69e
- this leaf
- f4d6b2ab3130c3747326a00803300a5d0b92607a26b986c6fa7245613cf4c0e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ysq5CT6VO9EU973xQieS+MpynjrIxfhEBEKtgiLs9tciVbtliy9JvAJp1QimWXI1Jl6kIksyKeXQ+v6vvH1jDA==