← previous blocknext block →recent activity
Analyzing
Block #108,494,404
21 transactions · 19 stateful · 2026-09-27 14:55:07 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,494,404 · 21 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
1w02w13w24w310w011w112w313w014w115w016w118w4
- 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
0x6b1259e6…4e11
0x1b6862…e19c
8 touches
6 conflicts
0xe15ccaf7…f81a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x49d58ea9…77eb
0x851145…3f07
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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)
6 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity