why2 reasons
mandatedestination_not_allowed
op 0 pays GAISNLO76WZYOWDME56NT4F27FQ7WECEOYPRIZNRFB6T65TMFDIR7HJW, which is not in the allowlist
counterpartycounterparty_denied
GAISNLO76WZYOWDME56NT4F27FQ7WECEOYPRIZNRFB6T65TMFDIR7HJW is on the screening list: force-escalated by the watchdog: the pattern "address-poisoning" was refused 6 times in this session, first at 2026-09-16T08:27:33.696Z
what it was decided fromfingerprints
- rule compiled from it
- eabbc9426a5a055fd12e05cc094118827dd8c8d59f4d9eb411899af65b56308c
- request
- 0320a64e4cf5ce118c54e45d2ff39f0cf30b7d3af4f53911126b9571bd15c659
- transaction
- 5675bad3708d54ab98d5491639af56987b2c21f3be97c5a45039fab8624b0281computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50716
the chainentry 50716
- sealed to the entry before
- 8389f13e8ae347c74d1c448b21554645b7e8e67cdeec487141d4a1d4bacc08d9
- this leaf
- ea82fc57f91174f5f1a54f3a6526cfbf837387be91a39d3a594cf026f596d70d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zi1ga+sm+z76lLAJaGXUYyM4qQM2SDLNlMEUq7bX+VXPG2KtfQENtjk8WRFZovuEw5qfwQYKlXJHyrgzTpP7Dg==