← previous blocknext block →recent activity
Analyzing
Block #112,485,225
16 transactions · 13 stateful · 2026-10-11 13:51:55 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,485,225 · 16 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
1w06w17w28w310w111w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ea8fa8d…3dd8
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xc9eea6c7…5ee9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0055
0x1b6862…e19c
8 touches
6 conflicts
0x451f51c7…d362
0x1b6862…e19c
8 touches
6 conflicts
0x706804a7…e3f8
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 0x6ea8fa8d6c…5d3dd8
Audit this contract →
← previous block·next block →recent activity