why2 reasons
mandatedestination_not_allowed
op 0 pays GD4JNXVMUUPVPNAYOP627GD6IQXQJK5S5DYZKSFQODIEHVMBCS4HOCLZ, which is not in the allowlist
counterpartycounterparty_denied
GD4JNXVMUUPVPNAYOP627GD6IQXQJK5S5DYZKSFQODIEHVMBCS4HOCLZ 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
- a7bdd8bad18e80d8de8c535b2c8e70e5371f89fe90dc6600c7417bfa26440323
- request
- 4f553301b7d11a74d6be543c945e9d9846bc3f1d8750a5afad9f5e6e05d14555
- transaction
- 4612806718f8931aa56396f55eabffa3e0e0e4af3ab13f4c1a9f6d1590e0fa19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2661
the chainentry 2661
- sealed to the entry before
- c9f0a2a5a630bdf1a076c6649e6796c6c55f07fddd53376c7f7918b9b122c7d0
- this leaf
- afc3d599c2620c6e358509341b5a67f39b89616381050a8712b26f0a3038924f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lvL43wPunsNpUOburLcFLVOdr3vZdzQtqSXaCcbdGdwNOfrl0G/O1old7tuMwXLnpZzIZkcSb5UQYh/inF8dDw==