why1 reason
spend_windowspend_window_exceeded
this would take GDSHH4AU4IW5JELZAJGB36LGYA66BYO27QSRGC4AXNRL3UB7SVZCDMPT to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- b3b4fcab3c63ae5522f7eaf8698683b33940aa7a6ecae4cdcde5982e99f01be8
- request
- d373907176cbe1ecc31faf764152a4820a8e0378261929997731ecde8617a326
- transaction
- 7375656b56379cdf793df3be352f63562510f782d266cda7a60a5edb914e4628computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62899
the chainentry 62899
- sealed to the entry before
- e5929fa9b1163885ff4c120573eb2cda8cc1f59f2fc99e2df17cca59159478df
- this leaf
- 5391444c5b779ae111588402d6027eb2b3dc1fe9669cd1a028b3d1eb5990943d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S4iLpufs0jbk89ThCK4abyyaTBiBeSuqvDdVVWRtScTaBTThreV1FQ/lVPsvHJdAR4hw2iqv3HvTbkcxZTS+CQ==