why2 reasons
mandatedestination_not_allowed
op 0 pays GDBOLMMSVC4IR3GC37F6NN3Z4YWBVNHGN2VO6NIO6EZPYZBAA7KOSUPI, which is not in the allowlist
counterpartycounterparty_denied
GDBOLMMSVC4IR3GC37F6NN3Z4YWBVNHGN2VO6NIO6EZPYZBAA7KOSUPI 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
- bb6673a67286975ca214c86dcf750d9939ca00bdd007b242100a37ea948d3e0e
- request
- feb8d9ec7b86daf960a5120d1399c1513a4a292f9245f1d397fbfecc96dc0a7e
- transaction
- 413670194034cddb6f8e2a8852b1abbabab6b7517eb585ea7a28a50a5147b44dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59789
the chainentry 59789
- sealed to the entry before
- 4f7f0200e2e467cb88d73783af01dc550d63b43ae03a05a3e1a83dce3fd724da
- this leaf
- 367bcbeb3b8c739b37c51cb76f0a887bdedfad7d926339db477d6b380f580b06
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eYmnlGb7woLhGP8Lg33KtoOrWzTA2WruaX5IRrx71lIu8QAhly3XzWUelaMDRpMcfbe+wPU/RDc6v140T27eCA==