why1 reason
spend_windowspend_window_exceeded
this would take GDIQ4YQA6EANVKMDYKAYRVN346XGJS6L7UV532OCJ3LUP3JICCNWOPJO to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 64879b6a54299aead9b0d44cc1c51a1e4841c5f3b9e76d9ce92d718682deadb3
- request
- 7445662c058d49e90cd0698089c5f675fad4037d1989f452a3d8e143ad196a0d
- transaction
- 983b65dbebcd978f725b12e06ac549fc0cb4a7d2a492edb1f17245dd61aedd0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52669
the chainentry 52669
- sealed to the entry before
- 7675f25e0738c1d1d6f6908d90da796bc117c13f7c889582e7a9908d570a50c6
- this leaf
- f2a5ea19f4bb5962155a0c89d67aeaac55e10b1f206919b036d294da5ae1b9ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ZXaIo4e7q7TLIC0VptlybAIE6MQKIq57/cuiIMxwtEwGMgilxwlKdYeg5NK+ot3hOLkVlhFIV2p2BW3hRlkDg==