why2 reasons
mandatedestination_not_allowed
op 0 pays GD4OE7Y3SX5AWV6AWLKY262FDGKVT24HHCI3CUIOS3WBBOMH6TMIH6YO, which is not in the allowlist
counterpartycounterparty_denied
GD4OE7Y3SX5AWV6AWLKY262FDGKVT24HHCI3CUIOS3WBBOMH6TMIH6YO 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
- ce4cdc1c15eb726344e946cdb6be9e61580fc83c5043d33624f7ec851b172e74
- request
- 6ba5832f9592ce104fc03003eef823347709365e5731afdf0c4a6e65b573535f
- transaction
- f6e4cc0025cc35f1c3dea777662e855c604d5b790cbd006a105aebad9693259ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20639
the chainentry 20639
- sealed to the entry before
- 71d7e8bae7c567d9dbe645229632ff400bc5e81d62e84b33dab7e4a91b730d98
- this leaf
- 8a138829cdf1f84c551a6bd07fc9f51761efd03b1fdd85b5d7d14fc5328aa70e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 242B0vdyLB+0Cu/z7cuaVa+G1HhPl/X5ITiGKwqTo/mRYUVnvDArTwRSZc+eDhtvDRgkuNItjRTzRe/gVEhhCw==