why2 reasons
mandatedestination_not_allowed
op 0 pays GCPSGQY4UBG5JEWVZI7STPSMZFNPDD6N3MTD7PSCIKPZ4K4OQKUKROP3, which is not in the allowlist
counterpartycounterparty_denied
GCPSGQY4UBG5JEWVZI7STPSMZFNPDD6N3MTD7PSCIKPZ4K4OQKUKROP3 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
- ba91a2604b457a0113ded3a2dfdd8772c3bd9ef8b810a6d21211a2b4b2e1defc
- request
- 7013174346aa9926aa3dfbb41859bcd119bdde603b691af4c6bb0c4886514842
- transaction
- 9aedc10c7b60596843dc7ff31e07fc49b2db13f41e92164a01f0af4a16b12f8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49531
the chainentry 49531
- sealed to the entry before
- 5c6c17654c82e5e3a18c96956d526704577b72165a27418064d049f3045df60f
- this leaf
- b6219facbf88eab2102925f5f172a229452173b23c0a7553bf771792110888d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z2p2m2aY1znEnB12q/CDQYqXuvASuWoxo6ef+GkrVZXsdqMFwF/6kwH5B8dbsvcFg85RetoVA88KKHTF3qlcCg==