← previous blocknext block →recent activity
Analyzing
Block #112,339,181
14 transactions · 11 stateful · 2026-10-11 01:37:09 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,339,181 · 14 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
1w02w13w24w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x928d6b23…536e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x67c17384…42af
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0052
0x1b6862…e19c
6 touches
3 conflicts
0x1aa19c07…50ed
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 0x928d6b23dd…ab536e
Audit this contract →
← previous block·next block →recent activity