why2 reasons
mandatedestination_not_allowed
op 0 pays GBU3UT3WYJGSEAOEFDNCT5LT3KUE4ECRIKK5J63XMSIPZCKZF2VQRP5I, which is not in the allowlist
counterpartycounterparty_denied
GBU3UT3WYJGSEAOEFDNCT5LT3KUE4ECRIKK5J63XMSIPZCKZF2VQRP5I 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
- 5bd7e66b0717678e97dd671c6829b5f43a757f69813952759f8ca2309047db24
- request
- 4050fe891ff6cad3e0543aa2519492d2169fea31f422e2d968dc0525e5c55eb7
- transaction
- 6fa6ae0874dfc66aac3fc54567099842476df8eaf7a68e948ee6ad2677c70c61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20221
the chainentry 20221
- sealed to the entry before
- 97c6fb7185d0c9089dc6610cf92cc81e284d701e6485f9c67d0dfc0ffa7b21c4
- this leaf
- 2c5612190598ebadc77683164e428bbad5aea5093e8afa6cd5583635729392ff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y8aci399RDxCfcrMXHqWs1Wohp+fiHDFyS8nwKPhjalFhOc0bhymAa6b5+5U7lqSp6DM2f/GURxT89Dr5rXlDQ==