← previous blocknext block →recent activity
Analyzing
Block #110,322,233
12 transactions · 11 stateful · 2026-10-04 00:22:50 UTC
Parallelism
50/100
Blocked
45%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,322,233 · 12 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
1w02w13w24w36w47w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46c0fe04…dddb
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0xc9db0f39…262e
0x1b6862…e19c
12 touches
15 conflicts
0x580c6fe7…0fe3
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
12 touches
15 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)
15 conflicts on slot 0x46c0fe04d5…f3dddb
Audit this contract →
← previous block·next block →recent activity