why1 reason
spend_windowspend_window_exceeded
this would take GD42IVQADPV4JTFODF4SGGRJZRH5HCTOGHB35M77G5MGJ4YKLLL47PBZ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- a22ffce906454758e25b4de2d960594a5535e31b9ac36bf301e5b3e08601013d
- request
- a3cf9d392bedec50185b8b1c9062a5afe3daa4464b079b139a33230c14153c52
- transaction
- 6e8f3ce6de96dcf024665feedd3ceb6b20f78db66df6567678a72399a3223b4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58307
the chainentry 58307
- sealed to the entry before
- a2becb92e976e3bbd840e5d8163a259d0d2ab064c8c08d1f23b98955b0ba76f7
- this leaf
- 0d0f7297df4bdba790d92e85cc12e286fe28f8ee5f78be85545c7bbfda7dc630
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eCTMNdKWJUUjJNbSpdvlfYRbHBPBkVwDM4pmr4AIemeHou5IgxQ2wZz036xZQZItuhUkq19rbnSWCFn7HTeeCg==