← previous blocknext block →recent activity
Analyzing
Block #110,308,226
17 transactions · 15 stateful · 2026-10-03 23:12:21 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,308,226 · 17 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
1w02w13w27w08w110w011w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x91ecc547…33ec
0x1b6862…e19c
8 touches
6 conflicts
0x4be03190…15ea
0xd32edf…ff58
7 touches
6 conflicts
0x7954ece9…fef0
0x34b655…2a6f
6 touches
3 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
6 touches
3 conflicts
0xd0cf1adf…82ac
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
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…000013
Audit this contract →
← previous block·next block →recent activity