← previous blocknext block →recent activity
Analyzing
Block #109,170,018
19 transactions · 14 stateful · 2026-09-29 23:43:06 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,170,018 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w17w08w112w214w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x33d5f79d…5ee8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…0009
0x125f12…a50b
6 touches
3 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)
6 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity