why1 reason
spend_windowspend_window_exceeded
this would take GDELVBG3Q3AZY6EOBHIE25M6VJIMUEFMBX35NARQPDUUBNQGGOCSBXQA to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 3e107abbd11c10d99bb0749bb3322ce0495e0364a84618a7372a6ff40ac5574b
- request
- e95cd7556ee3fcfc59f3650f44dc69048b2f99a40358968f4f7335032839a685
- transaction
- 2e4c5ef055d07022876952466a88877f6c53d2b9ecf63223d34137b5dc00e22acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47036
the chainentry 47036
- sealed to the entry before
- 49f683c9b34c6a73c20a7b9865b28bd5f3ceb928aae1c28434d3b0dfda47dd3f
- this leaf
- bb451efb691e3450d64c735cd20aa83b3539e2c0e4a9a53af455aeb02826c035
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f14Hx/dR2dZ0FnGvCk80DnnAZBCfYuIMHMu0NQNznEJDFDCC2f8j2OrKQJVBWNL4TdDj6OrW2mFaIrWNZdJ8Ag==