← previous blocknext block →recent activity
Analyzing
Block #107,816,108
17 transactions · 17 stateful · 2026-09-25 06:01:17 UTC
Parallelism
65/100
Blocked
65%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,108 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w18w29w310w311w412w513w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xed863ec8…90dd
0x1b6862…e19c
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0xe44c2c65…ccc4
0xd32edf…ff58
7 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: ShMonad (shMON)
6 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity