← previous blocknext block →recent activity
Analyzing
Block #110,371,244
18 transactions · 17 stateful · 2026-10-04 04:29:25 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,371,244 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w19w412w314w016w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x485d2778…aa5c
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0xc707b632…98a8
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0053
0x1b6862…e19c
8 touches
6 conflicts
0x062a584e…0f5c
0x1b6862…e19c
8 touches
6 conflicts
0x7fb41b08…7e1e
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)
15 conflicts on slot 0x485d277847…5daa5c
Audit this contract →
← previous block·next block →recent activity