← previous blocknext block →recent activity
Analyzing
Block #110,198,324
11 transactions · 11 stateful · 2026-10-03 13:59:19 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,198,324 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w18w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xb89c7e78…0bf2
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xc000f184…32a9
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
6 touches
3 conflicts
0x5fdc7de4…d6eb
0x1b6862…e19c
6 touches
3 conflicts
0xa97e0bd1…46a1
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)
6 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity