why2 reasons
spend_windowspend_window_exceeded
this would take GDWZDBM4MEOEVWWEJ3PXW25PDXTZIZDD27ZWRHUBQQE3JYZQ3EDBYLGI 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
- e3fb774299b406077a590a6cf5aa60a3814ad6f2aa3432edfc80a0784df07f58
- request
- 031f9966eb8ab47e326026aafefe02f121ee66d25342870ec8e9303dae9dd082
- transaction
- 9cca0e7e3f1f216f83c64a40d856399100754f79782c9ae300d517fb81cd8326computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8252
the chainentry 8252
- sealed to the entry before
- e373cd1759b2342d9991db8e820c2aa6ea359bafe368a3ed6688cb788ac1701d
- this leaf
- 7f6fed6ed73e1e9ba75713b4a4056cd9d935088e4690420a9bb9e33e7d2d8471
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Rjm7kKUhJl8CKIBp+bVBzbRJznYqsdCdb7/bEN0YN7ARzeAayT+Af6i14k6bZiirCZxq/RuKs8KzVq4wo8IQDA==