← previous blocknext block →recent activity
Analyzing
Block #112,370,198
16 transactions · 15 stateful · 2026-10-11 04:13:12 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,370,198 · 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
1w02w13w24w35w06w111w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd8d828a7…b64a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xdaa3cc95…f835
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0x8938e11b…25f6
0x34b655…2a6f
6 touches
3 conflicts
0x2b1e2c2e…8f75
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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)
6 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity