why2 reasons
mandatedestination_not_allowed
op 0 pays GB3P6LUMI3253EYZNKYIXLY3FFBJTVJRKJ7C3G2QVUEMP33QCXEE2EX3, which is not in the allowlist
counterpartycounterparty_denied
GB3P6LUMI3253EYZNKYIXLY3FFBJTVJRKJ7C3G2QVUEMP33QCXEE2EX3 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
- d0af58cdc336ec5ebab9c70461e552cf7dc8e791a786f390d281ec331a5e6f7a
- request
- dbf4a4d3af5570c0dd961cffd8b0e3052e7c0ffc0871328bc11a23d8e69be57d
- transaction
- 5afcf82c5eae5706d0895b12d401e60de6cc9a23f7daae0988c72fa2c36f74d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24945
the chainentry 24945
- sealed to the entry before
- ba0023880f927d7e4485c34ef61251ebea6c0208c145f585d984740a0e3e51c8
- this leaf
- 565681008420ce6fbd0801501c1d03aa084eb8258b4942da19dffcef8c8a1c3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5T0NZ7JpwpC5Ggn96iwLvFcinj9vKOSYGd1DTJJsYDwuiIs7t1NxsH77IuDpo8JbItwlK6KlEHQRgyvUmayuCw==