← previous blocknext block →recent activity
Analyzing
Block #110,322,115
18 transactions · 16 stateful · 2026-10-04 00:22:14 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,322,115 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w112w013w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c6f37ba…c206
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x1ccc32f5…a814
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
6 touches
3 conflicts
0x0d9d9e17…178b
0x1b6862…e19c
6 touches
3 conflicts
0x7896cd92…9c99
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 0x6c6f37badb…87c206
Audit this contract →
← previous block·next block →recent activity