← previous blocknext block →recent activity
Analyzing
Block #111,676,838
17 transactions · 16 stateful · 2026-10-08 18:04:39 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,676,838 · 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
1w02w13w24w35w47w08w19w210w312w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x580c6fe7…0fe6
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xbfb0c497…ff2c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0055
0x1b6862…e19c
8 touches
6 conflicts
0x46c0fe04…ddde
0x1b6862…e19c
8 touches
6 conflicts
0xc9db0f39…262e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x580c6fe77a…cf0fe6
Audit this contract →
← previous block·next block →recent activity