why1 reason
spend_windowspend_window_exceeded
this would take GD5R3AEZMFSGNAPSCNVWOJLYQERBC6FR4UZCIP7C52P3CWMNG755TNHQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- d4119add3a963ab9e71b795426d13f2f05f3e48d8d2117d469a61c0fef3b5b10
- request
- 7bdd17f8c702beec554a606bc86253a3049ff358ab9e977573627109cf68b617
- transaction
- 5d54fde6559fb87fc65f160585c2beaf1ed9c92d9a1fc329c268810a96dcfe06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23562
the chainentry 23562
- sealed to the entry before
- b750541021e389e5c0ae182fe2a275736b3c40eab9571e919b9c1ca44926ac1f
- this leaf
- 27ca53bb7657033b2f44aff18e4c6520b529a3bc2a52672186b937cdbad3494a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cmhZVsx+HWd8Lncq9YaXB4qgzXdRwCHBaMQIqLEo9mTPEfTByEd4w82WkHVb5lLtIXnasFEtsCOqfhKwOcfODw==