← previous blocknext block →recent activity
Analyzing
Block #111,071,913
18 transactions · 17 stateful · 2026-10-06 15:19:15 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #111,071,913 · 18 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
1w02w13w24w35w46w57w610w416w317w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1526c23…f2b4
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xcd455448…caac
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0051
0x1b6862…e19c
14 touches
21 conflicts
0x48f92a13…4a05
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
28 conflicts on slot 0xb1526c23fd…dbf2b4
Audit this contract →
← previous block·next block →recent activity