why1 reason
spend_windowspend_window_exceeded
this would take GDQ2RA7ZPB4KJFAFVVVIH4QSHORQQIECKIV4OQCPCZQN3OC7QLE2BFBE to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 839e4fad7b72e2a55cc2475c10dfcf5224ce52156ac907a1bd049aaf71fd2892
- request
- c2e0c28eab87b58883a38d56bf6f60acb0af83f4a90603ab9434fa279e411ee4
- transaction
- 214033b74e88b8d623c1b3f94f6072b52d83cb8d5a25af40d7cafc3610a33a4bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13060
the chainentry 13060
- sealed to the entry before
- 9fae3a20fb297e54989c8d8b568fbfd9c9efd6bf09799d3eb1ea31640fd69fd8
- this leaf
- 8cff6f7f41d8c1c5fed6632a96a5aa936647282b18907a1c5a3a5c59a424bbf3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bI0DhdN0L6SH19gsFfiq5dp6hetlfPNs7C/BQ9Tzi1gFXFQfZgDoPiY0s0cSc1yOG8y2IDqY7C48QGSn6TUlDg==