← previous blocknext block →recent activity
Analyzing
Block #112,344,535
16 transactions · 15 stateful · 2026-10-11 02:04:05 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,344,535 · 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
1w02w13w24w35w46w07w18w29w313w314w4
- 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
0xada193dc…5c7a
0x1b6862…e19c
10 touches
10 conflicts
0xe68f99e7…744c
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x206cc6c8…0159
0x1b6862…e19c
8 touches
6 conflicts
0x6f0f03f8…f3dc
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