why1 reason
spend_windowspend_window_exceeded
this would take GBDK2DBYURPUINJEDTTXTPEGBMPCXAA2EZLLIKZCJWFKNWOEBNFRWZFC to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 98692ba8cff3f9c7ea2812088416617ef308b6fa47e385b00355aed51f10c4de
- request
- 2d526017ba803cd5743e4f0e570fe98e9a85d1ac557103c14b567309dcc70bb4
- transaction
- f7e78ee8ae1adce622907e1f24ab75e10a28316ba6a358a30fe727e9844ca2facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21950
the chainentry 21950
- sealed to the entry before
- df47ea673cc395d5d35cbc5a3f385686a2e8e01e7c99ce5bd19cd4cb0891cf87
- this leaf
- d1c638f82a909ff81cbba4ce56c59a6af6e39bfb175ea34358bcc2cc6f470546
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pyAKrc40WeoLRsV7c73oYDVzs7uHrCyRkZIikNxeB09DirAdBHieVthMyYwLeVcBMFR1mvhGe0nqIArwOm5zBQ==