why2 reasons
spend_windowspend_window_exceeded
this would take GD3PK2T3C7LWOTJ4OC3HVBP5R7LO2VJBBSBT72IDCSXKZHQ36O5LI6Q5 to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- e1edbdd9237211df1ddee6edacb5cfa5a65ac349184a4cc66de41e7b88446c4d
- request
- 163de4eaf80b7e0f3215ba4951f740fa3d08ea9a2dfed29d9d103f94a6e867d0
- transaction
- fec54fbe0c5b17cbd963c5adbbb34652bf0f5d9d785667b0ba8fb70dc56cbe6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26115
the chainentry 26115
- sealed to the entry before
- b6c10fb1fd37fe29068e64abd3939956f1e283f815d13a61230056d455e58445
- this leaf
- 0a2772946ebdb2d4515dab718bb3e97f58febbb1c0e947dda10f76ba52875582
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KN68X5e0JKhjEDd12qn51jsFH9AyWlvUe/Ma67IMaGMz51X6MRI5eU/FS+xOpZMv19O4SilC3QkgmalRBafRCA==