← previous blocknext block →recent activity
Analyzing
Block #112,235,692
13 transactions · 13 stateful · 2026-10-10 16:56:29 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,235,692 · 13 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
1w02w13w24w37w18w29w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5b10148…e638
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x0f207de7…52cf
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0058
0x1b6862…e19c
6 touches
3 conflicts
0x3c31dae6…dc04
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 0xd5b1014813…d9e638
Audit this contract →
← previous block·next block →recent activity