why1 reason
spend_windowspend_window_exceeded
this would take GCHGCII262ITPY7CDZXII623RBU53CGJXSZCCZIBXGANXE24LXNCP5VL to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- bf0182dd4b169f61266a63b5c7cc949706ce7f94696c9d76afb08362e29ce4df
- request
- f2cf109d397358a5870556ab79c99129f73310af998eda3cb31af1a42144d16e
- transaction
- 935fd1af4e93edc711327b4ac2119293d175a599eb3f61d83435dd5d1390ae92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21615
the chainentry 21615
- sealed to the entry before
- 7260e311d8eceeb0399dcbd3d093b97c51bee792062c0e287818c7f0f47eabd6
- this leaf
- 05bfa3a28f821749d1eeaa0eab23973d9d79b392e99ab31998c6ae32717e60a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- STj9m+1+e4tbSNiMI86g8LkQcsSR9Y3hAYcrWOuQuWBVniNAa/I3PY3o0xVFLEIUxr8lWk9M9Y9GLccU5guNDw==