← previous blocknext block →recent activity
Analyzing
Block #109,144,366
30 transactions · 25 stateful · 2026-09-29 21:34:02 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,144,366 · 30 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
1w02w13w24w36w07w19w112w013w116w017w118w219w227w128w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6071d1d…4967
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x68f7aaba…88df
0x34b655…2a6f
8 touches
6 conflicts
0x4c80e1c7…4c84
0xd32edf…ff58
7 touches
6 conflicts
0x4862f4d7…5fe1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xd6071d1d86…374967
Audit this contract →
← previous block·next block →recent activity