← previous blocknext block →recent activity
Analyzing
Block #109,144,705
19 transactions · 18 stateful · 2026-09-29 21:35:44 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,144,705 · 19 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
3w04w16w07w18w29w310w411w212w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x394c3833…b4a8
0x1b6862…e19c
10 touches
10 conflicts
0x9833a2dc…032c
0x34b655…2a6f
10 touches
10 conflicts
0x255aae44…d660
0xd32edf…ff58
9 touches
10 conflicts
0x4aa45c58…bd34
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity