why1 reason
spend_windowspend_window_exceeded
this would take GDZZWWCCUT76YMV5A3YDU72LPT4S35IYSK5QJQWADRRM6ARIAOU2R5AW to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- f50a829ce7b158ddf326d65de899aee7c3cb03a26872b01f77621ee012cbdb25
- request
- 830ace354f89066b21ba36c9669b2f0913790364922d8410791705458bfd663d
- transaction
- 26d89e48bdd8e090693d69f1b7cc0b2ef168ea18c5c4a1ca055a39e11dcd082ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29118
the chainentry 29118
- sealed to the entry before
- cf8691bc737e8b6663335cd26b7a1fd306e0e39d06ac7305568d86a1120961c3
- this leaf
- 7fbb5a9c8c8cd464d334bc4d759f3e1aea3f89a710d7d68412084b0521c1d1b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7tNuM6m11LZhLePPCybBjrFZCfjWZp7o1wTb0kmnu78q1RbHWa8TtKvo7LU35F1aB2EdsoRDC9gqsO9R5mF9DA==