why1 reason
spend_windowspend_window_exceeded
this would take GDE2W7HLTBUMLK4FTAVKJ3EB4GZOTUKKGGOF77X3O5MQH3YTK45TBDZT to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ab440a152d425cb6c97684656db0af0427a995c0ce9804287efdef9ba5b336ac
- request
- d2a6ac784ac7e9d95ac871bdd874d40ef6bbc4b2b792bb630d39fb9d627ad0f6
- transaction
- d2295cb183683249e3865715dab9072e2f8b18ee2552d8ce6ee9da69bc18d294computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35271
the chainentry 35271
- sealed to the entry before
- f46148d55772b395962b625dce5c4956a4d899b8cf9c9be95ce88df53a9924e3
- this leaf
- e8bd55687c5d488a7617ea14f28bf0d13b8a09bcf4659caac72826e073d3d2d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8V/7zMLuImeNgBdd0RVFW+W8Ae4G9xY0WGM7jNZylgO1hftxUVfke5KRIorVAuylYp30mhYa7M6wB/0XIaKaCg==