← previous blocknext block →recent activity
Analyzing
Block #109,176,754
12 transactions · 12 stateful · 2026-09-30 00:17:00 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
1.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,176,754 · 12 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
1w02w13w24w35w46w07w18w29w010w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb82
0x1b6862…e19c
10 touches
10 conflicts
0x6235638c…6438
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x20555465…c2b2
0xd32edf…ff58
9 touches
10 conflicts
0x5086c64a…28ba
0x34b655…2a6f
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)
10 conflicts on slot 0xcb45d9d62a…b1cb82
Audit this contract →
← previous block·next block →recent activity