why1 reason
spend_windowspend_window_exceeded
this would take GDX2QIRV4WHYEOJDHN42SUPKTUIA3B6RF7XMBGJQVG5PJVFVLHMBW3XY to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 8eec2c116b6f702fb127917e7681b7d84b2e9f273c78d9a2f70688d76f7820a6
- request
- 839dab59d76f61c78b81dfc1f0b9372efe55bfc1b93f7ba5f4cae591e4a2e62e
- transaction
- f3d3b33714a72406068ed3a5c9750d96db004f2b5eb344f26de3d58bb85da963computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54697
the chainentry 54697
- sealed to the entry before
- 20d2587e30ead4a32ad608b72e3c07b9ed711da26b93f8c517ee82aae7797638
- this leaf
- b92dcb9f43d1424898e80083cff7f4eaae7d5db570acc4da43e02798fb50847d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZDpIV8POinLfOmRHhBcL/0nvaie9agup3xhBqYZR/IMsdu58Ib2tik1PJ91rSXMIddk2fSzEI4cAb4CTZeGwDw==