why2 reasons
mandatedestination_not_allowed
op 0 pays GDOZS5QGLRS4575CZ7ENV5XUX2MXJUDOCA6UZRTFHU5PUEMCDPQAX7A6, which is not in the allowlist
counterpartycounterparty_denied
GDOZS5QGLRS4575CZ7ENV5XUX2MXJUDOCA6UZRTFHU5PUEMCDPQAX7A6 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
- 153fc710a4c0c3aa307e4a0600e0a297b28136b0d0e2cb01f206f15844ea22e4
- request
- c7b2d64e27fbb3268ee212f8ab022d5a7813110017a49f1a83f853ab6ab44df5
- transaction
- b2adb481181f6526648d3ff390651aec3a8e2971266f1a64ede978fd773a0150computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1836
the chainentry 1836
- sealed to the entry before
- 0e06b2f2b7c754d2c8f33ec8544024a9c1bfa2662caa452219c7c7227f3aaf3d
- this leaf
- 31134e2040225c4fb8329eb3451691e5b589de9a530be3c307f2761169a3c749
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JkaACnO4UtvQmSgjr+Z5UnlW3PnSVkg693Pse1Db0DfP6gj7WG+uqQNvN5hi2MV3cgr7hATh/3mdh3cnSV8hAg==