← previous blocknext block →recent activity
Analyzing
Block #108,952,297
22 transactions · 18 stateful · 2026-09-29 05:24:05 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,952,297 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w714w115w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x7d4f80a4…bb18
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xcf78fa1a…ac79
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0056
0x1b6862…e19c
12 touches
15 conflicts
0x2df68f10…0a9d
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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)
28 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity