why1 reason
spend_windowspend_window_exceeded
this would take GCB3GRNMVMN34PJNBKZMJF3EHB7QAAA6UIFPB2ODVBK3OS3UMGBYZTYS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- eb9e40a5044d32d8a6abd6c6038bcf070d77459016d761d32ef0f4e186292a36
- request
- 8e72c0cd9102a557c4059fd196efc8732c526ac89732607a78272ce23b94167f
- transaction
- 38d9f4092c804daf66e021693b87824a9af5f4a401e011a634bcdc74bdebb55ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33050
the chainentry 33050
- sealed to the entry before
- 834a8fc2d869b3fec5454421dbee028d8bffec763926c44e0c644736f892429d
- this leaf
- 8b7c3e6daa8bcf0bb69c47ccb6c5540154a2332b08f2f317ad6ddd1a885f15cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 14aNkBEfVZdYFRwx7HAp6dazji4xSswgIdRKA7tSVgDO/soLUpQ2U5cPjYnqw05k4YoEVxatN/rnTNlyxuRcDQ==