← previous blocknext block →recent activity
Analyzing
Block #108,678,001
24 transactions · 20 stateful · 2026-09-28 06:19:41 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,678,001 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w26w39w012w115w217w421w022w123w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x9dce5f78…29c0
0x1b6862…e19c
8 touches
6 conflicts
0x5274ee02…6a20
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x842db5f1…6d4b
0x1b6862…e19c
6 touches
3 conflicts
0x6f5d1ca1…f1bb
0x065c9d…c394
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…000015
Audit this contract →
← previous block·next block →recent activity