why1 reason
spend_windowspend_window_exceeded
this would take GAMDRHULCTCIS2XLCPL4A5JTPRVE6BQCFHJHPMHMJODDCQHJLDJB3TNP to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- edd46d8585f476ca699ce0caf3bb751f7cbbb6390fe6de1972cc8ab4d9014be4
- request
- 788898ee55687bd9ec1ba4fda0057146419f0b58861839776ef25871b252370c
- transaction
- 6bd21eef06e4c61f75394e21309c43dfabb1bf4a44bfe8fda676af58d01109f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41432
the chainentry 41432
- sealed to the entry before
- 673e9dcc8705949f2ccfd02fe8186ad6375747a1d2f18480e156a835a7876a2f
- this leaf
- d7a24e3ea1197ffef6598ad32919426f4f4970a5363c2e2725e900727491dc0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YPhuPSxFjXmGYi4tzYK0SWR27l6dig7KPliKVgviNFVbAdCtXVObutAPI06lF05RrN0ohqIOKr5xfawg9mWpDw==