why1 reason
spend_windowspend_window_exceeded
this would take GDNPMRYN5HJCX2DLEIJYJVNPQU4RGGEGSGNZBRM3WEBADSWRCTL256KS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- dccab741c279f5e37f52b4555d974f04bd5517fc63c8592162d226d0409cbf5d
- request
- ef1e73422d94193b915f73129a6542a6aba27c9c885fb7e271d713af887c1f96
- transaction
- 46fab57b6cf2c8552f3cbb80a8c603df37854d8e86e81d82c1561abca4b7157bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4150
the chainentry 4150
- sealed to the entry before
- c89996dd12c6655efa876329c890a9d369dd4888a6dc87f74ff2d9cce6ce3645
- this leaf
- 20cbbaaf59364d0b217fe6ebea281197263cbdd718a4c2d7ffc21290c7069eb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KIDuIiEjMROS57QGGeZ6VjaVkQ0vHGudHZralIr6belFXpUSCnYZF8++b4CXS005Gc1A2lWkzMlvo+7i/ia9AA==