why2 reasons
spend_windowspend_window_exceeded
this would take GBDPJ5N5XGLQ4XWOE5T6FWQUBH5LLOQLZM4A4TX2DEJ6YCMEBH4G5JUC 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
- 5ac6a8ae5f99208ec6a756632f6d0e1f5b27af1ff6c66c8eda80ac05b940f8e2
- request
- 2de3dc67d107634c3663057a7bec9f99313f4c0d8bfde78963f68789a02f37c4
- transaction
- d99e03e0b69da5d4879e8cf2cb29bf0df34ec01ae89245935abfe17a9211054dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15205
the chainentry 15205
- sealed to the entry before
- 6051325d12a9bf3e7d8a1d4a88ce892e12ad6ec3ffb01ffcf87326f03c18179a
- this leaf
- b8a446dbb63e6f9b06e2ef594bf3b057e600a52f40b3c208837d47e917741ce8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /DR2qTZHG/38RPcX4JJU5+WwMdUKWzCzS2RbPMwR6/ZQNySSfkKFi9wli9IvQMgCPP7+0bViHSnJAe3hj+otAw==