← previous blocknext block →recent activity
Analyzing
Block #108,969,050
17 transactions · 13 stateful · 2026-09-29 06:49:09 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,969,050 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w29w113w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d2f
0x1b6862…e19c
8 touches
6 conflicts
0xda70f3cd…e9bb
0xd32edf…ff58
7 touches
6 conflicts
0x30f54ecb…ab9a
0x34b655…2a6f
6 touches
3 conflicts
0x744d62c0…0137
0x1b6862…e19c
4 touches
1 conflict
0xb4836f9e…a9bc
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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…000013
Audit this contract →
← previous block·next block →recent activity