← previous blocknext block →recent activity
Analyzing
Block #111,064,984
16 transactions · 13 stateful · 2026-10-06 14:44:14 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #111,064,984 · 16 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
1w02w13w26w08w39w410w013w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0ec60a1…d240
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x5da265d1…da4d
0xd32edf…ff58
9 touches
10 conflicts
0x398c985c…810b
0x34b655…2a6f
8 touches
6 conflicts
0x5e86ca39…99d6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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)
10 conflicts on slot 0xd0ec60a15c…75d240
Audit this contract →
← previous block·next block →recent activity