← previous blocknext block →recent activity
Analyzing
Block #109,176,529
20 transactions · 17 stateful · 2026-09-30 00:15:52 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,176,529 · 20 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
1w02w13w24w35w46w57w68w09w110w011w112w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x0f94ee4c…1899
0x1b6862…e19c
14 touches
21 conflicts
0x64755615…c178
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0053
0x1b6862…e19c
10 touches
10 conflicts
0x29607f71…4bff
0x1b6862…e19c
10 touches
10 conflicts
0x96faec68…3b1b
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)
21 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity