why1 reason
spend_windowspend_window_exceeded
this would take GCUBRXBPMRJDEWMZ56F5XUZ5QSX5E67TC2JIRUBWGMK6LEYNAFTCSF3I to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 884f061c4dfb14a00cc23ef9f3fa8f43d0c4377716e66f96d45753522a1079d1
- request
- 187404f4394807fdbd1612cfc3b8c7688b93c931095f24b9cde66283eef6eacb
- transaction
- 5b5d5a0ab77b16931e7827ecf8f0dcdbc831199eb183ec47f948c384624240cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13802
the chainentry 13802
- sealed to the entry before
- 74b8052c79e8fedad1dbf392870359868844ad5bfb2ba729567762ecb388a036
- this leaf
- 216217901fd1490e756c70f8fc57305841f3d7e85048cb7b44ff247bf9392d9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 89EoNyzcdfpyjdPlbujw5ssjjpxn9nS88yCk0kgIhC8dIxl0ZeFh/1guO9tUP9oL7zfNMqJQCf9DhIf9lUzdBg==