why1 reason
spend_windowspend_window_exceeded
this would take GD65TOEOVIOUBI7UOKJHO6OI2IVEAAWSOJXLHAH5SI5MLHE57GS5HD2E to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- d28a64f9da811ed756f7d6cd16c409c8264231dcbeaa031db503b3b012833071
- request
- f6f70b9826f0d39633a0da93a803e9da7305f24144582dc3adbf3117ef44f2bd
- transaction
- 67e4287ea7bdea40561448afc64fe846f58941928c52a05a16b3eb2030256fd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41554
the chainentry 41554
- sealed to the entry before
- 3bac5b81eca8841e8fdbd1c885685d40ba59ec623943af2aaa7dc2ad43d66d18
- this leaf
- 47468be76076c843b9f5f45266f07859b9aa0353ff7551b7672fa198e1575589
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8sMaxg3PAyEyBrupKlt1BG42+Q4qKX0H3P94JMd+rg2QhcLwdqRKBcSqop46SsJgfGISsI+ALjLh10+6o2nPAg==