why2 reasons
spend_windowspend_window_exceeded
this would take GDVBEG3KFX2V6E7GDWUB63GPXT35HXDDZAJ6XV2ZE7O2XVZTLMMEQS6B 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
- 05fdae409c3598dc9f3ee75aeac4c372679cb46ce8e712e01951ebfb95574db8
- request
- 5db564486aca918b9c30b43749cb157d9a3cf1813066ce356bab5a1baa58b543
- transaction
- 6e992ccaf4c7e33ecf9ef75d9a1e0bab46a86cf242499f9a914860e8137ec0bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7992
the chainentry 7992
- sealed to the entry before
- 236c20b49e9357cca57f9d5c66038fd54b4d1230916cf96e0112baa77aac8369
- this leaf
- ffb779bab64f8dd87400e4f4511fdeba448d2bc7a0dffb5ef430f4efcafc437c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dx06dycAm8iX6pu47td0SBU3k5dNfmZ4w+bKvibxl6I4FjeGevhzzAbAwwvkWmfsb14srnqnyo5auF22E7dTAw==