why1 reason
spend_windowspend_window_exceeded
this would take GBFGMNMN6NJRR2NEXEFQP43JQSJAGCASQQVXS7EJ3SSCEZ7BHITYL5YA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- da756aed14dbc24fdb990a36145f5b48c2774a542ca4024ce36bd243137b119a
- request
- 40c1b75ff4e9b80d2841a708e008ff19d68bc206a3e6e1b894b7868b569b52df
- transaction
- 4b6fc00439f4d87c5caa55b21ab6f64e3b880d432b17ead60d2e7ac7df1a779dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62091
the chainentry 62091
- sealed to the entry before
- f2dc82f5529e0eab109ab2c709312f321c81884c93cae6715312b309a13bb0d5
- this leaf
- 4de300f3382ae599c794417928c4021954df1b6d962c608a16e1a26ddeec3c3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LFi8loaLIc/+gYsZ3Jl1tdXxfIx1hjirwcVDgNJtGtxt+6YW126T9oVo1JoYaktZIaNXh1PwK0rhIPlOIpK+BQ==