why1 reason
spend_windowspend_window_exceeded
this would take GC7WSLXB6ZVT2NU6PYTCXKW4F5C7PLJ3EWXZTSF4L36PV35P2BAG4LBH to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- f243c49f3f44697246b9e6e485549d9054d007a7072a7fa0b907198156405715
- request
- 098a771d996055c43ec9296ecae68f7d0681410e40f31bdff7b34a2cf9dc4a57
- transaction
- e793a300f33a8918e4619fec2323d0bf68fd215c633a596fbab6e13721711c64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40253
the chainentry 40253
- sealed to the entry before
- c7cf9b82dff59733a92dfa3d9361f739284430f542d64f2b71acab1bddd899b8
- this leaf
- 9f0cedc1ab104c4b865e9de9e569ee7c0ef4f16eeb71ea1b07fff9eab0f807b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TdAlMhvH343I/5mBB4rTwUDY7oOn90GnL76PzsSSKZulyvXRDCe1r4e/bYp081sxOzUdzfPRFrJUG8/eqMU4Ag==