why2 reasons
mandatedestination_not_allowed
op 0 pays GB3T2EYGQPVL7DTMU2M4MIIZCICTJ42FTHSTGLFVEAX53UUX6JSZKRWF, which is not in the allowlist
counterpartycounterparty_denied
GB3T2EYGQPVL7DTMU2M4MIIZCICTJ42FTHSTGLFVEAX53UUX6JSZKRWF 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
- 6146fdc3b5a0a34d6825813579ffb672eb5d3b5ed6e45ecb16b0527acc8a2469
- request
- 63c09889b7db7e68dc7e4fe1b907613960e6678ada033ae6aeba3d0b00f68638
- transaction
- 491b628faac8ddfa12c57b78eb3e69dc7f4104e3db1c659cab4e927c6a030c32computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54618
the chainentry 54618
- sealed to the entry before
- f33691a0b2b175181b5be05aacb72ea11688772a554e7646c40b070990a6c470
- this leaf
- 10ec4d2f6714e90bbd95699706012b6b74ba3e2a6c2c03a56e7dae660d16a8f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TjZ7uS9d020zQL22mFmebvO8/hM+JzVhajFU6P9FgQ+MG1tZxikfrmuy0zrLStfMErseyTROsnPmmXIwh6m2Bw==