why1 reason
spend_windowspend_window_exceeded
this would take GDTMNXCD4FN7YY7GOBG3Q3BSETP3HGVDFYZN2ZJY7KM7DCLQB7PQSDKE to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- ff186fc8efc2889bec64715439773101ee58604e891648505fb78d9eacbde159
- request
- 780e5eef8c4e69bcc1d5c207ad6cf8fc69fd3e480cde53ae390c05787068579a
- transaction
- 2597f53045ff3203b3c297c80cedecef0c35d5aa295772034ff180cec3713f3acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9668
the chainentry 9668
- sealed to the entry before
- a67a4b94b144003a3cbd2e53b02652464d3f90a26048e6593e8da878215002b1
- this leaf
- ab44ff6713fe0022e50b7cc55b43b7b821b90deba3d458e732c6add65385b652
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7BojtyG8maQh6Lb/YyZuMa7ktyAa98/vPS3Xp461U1BgzXPE+btZVdIxVIekRCvItbRJryFTwEgBcHKaBO2DDA==