← previous blocknext block →recent activity
Analyzing
Block #112,610,584
20 transactions · 20 stateful · 2026-10-12 00:22:39 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #112,610,584 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w110w011w112w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc2aacf41…5504
0x1b6862…e19c
10 touches
10 conflicts
0xd85e8991…20f5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0058
0x1b6862…e19c
8 touches
6 conflicts
0xd5f4af47…cea8
0x1b6862…e19c
8 touches
6 conflicts
0xd749e32f…5cc7
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity