← previous blocknext block →recent activity
Analyzing
Block #112,355,666
20 transactions · 20 stateful · 2026-10-11 03:00:05 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,355,666 · 20 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
2w04w05w16w28w29w110w011w113w316w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x394c3833…b4a9
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x1bc2e4bc…662b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…0009
0x125f12…a50b
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
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 0x394c38330b…c9b4a9
Audit this contract →
← previous block·next block →recent activity