← previous blocknext block →recent activity
Analyzing
Block #112,492,369
19 transactions · 17 stateful · 2026-10-11 14:27:52 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,492,369 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w113w214w315w416w5
- 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
0x14d1bf0e…e09d
0x1b6862…e19c
10 touches
10 conflicts
0x15bede2e…6e3b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0055
0x1b6862…e19c
8 touches
6 conflicts
0x1c2bd0c3…36ab
0x1b6862…e19c
8 touches
6 conflicts
0xb7358e46…0bc2
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