← previous blocknext block →recent activity
Analyzing
Block #111,843,405
33 transactions · 30 stateful · 2026-10-09 08:02:42 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #111,843,405 · 33 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
1w02w13w24w35w47w021w022w023w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6cb118…4caa
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xfd72d8ea…13d6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0058
0x1b6862…e19c
8 touches
6 conflicts
0x03e975a9…7ce1
0x1b6862…e19c
8 touches
6 conflicts
0xca2a5765…0397
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 0x0a6cb11882…264caa
Audit this contract →
← previous block·next block →recent activity