← previous blocknext block →recent activity
Analyzing
Block #111,666,734
25 transactions · 24 stateful · 2026-10-08 17:13:46 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #111,666,734 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w112w213w314w520w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bd55803…5d4c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x833ee023…ae30
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0055
0x1b6862…e19c
10 touches
10 conflicts
0x2cc82ae4…16cd
0x1b6862…e19c
10 touches
10 conflicts
0xd366dec4…a7f5
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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)
15 conflicts on slot 0x3bd558039d…705d4c
Audit this contract →
← previous block·next block →recent activity