why2 reasons
mandatedestination_not_allowed
op 0 pays GDTD5GVPHYBZIAXFAR3VUUYNHOKSLE736L4QRBSMDMASO2CPVI6BYJKN, which is not in the allowlist
counterpartycounterparty_denied
GDTD5GVPHYBZIAXFAR3VUUYNHOKSLE736L4QRBSMDMASO2CPVI6BYJKN 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
- 38cd030d9a33ae8b051bc4c8098ed4bcff2ccb62d05b07fa8d0c58ad376518a1
- request
- f573f467d458297e8ce77d556fcef820b0aa26e61adc57b367e239e674d3b9ea
- transaction
- e6df8c7d4de6b3d5da67ad06a09dfb12359c85c083d0d2fdfc6d8b02d6fcaa57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57027
the chainentry 57027
- sealed to the entry before
- ad724fdd5316910d0abff16b2988cb32ea7833d2afce8ecc67e909e704ae4eee
- this leaf
- 6abfa4f892a8ee68a08923a170c3237cc9c804b4eddcd88c12ab562b0091531a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B6ejTqxpOMt78+iETuLeDDoeLPFVXA5AIHJQXI9vojraVcZqZurNDa9a9hFKNS2/WAb9I8XulngAasXHKLs1AQ==