← previous blocknext block →recent activity
Analyzing
Block #108,366,767
17 transactions · 16 stateful · 2026-09-27 04:12:42 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,366,767 · 17 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
1w02w13w24w35w46w58w09w110w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
12 touches
15 conflicts
0xcac0dd3a…4824
0xd32edf…ff58
11 touches
15 conflicts
0x0778475b…bd75
0x2a68ba…90c5
10 touches
10 conflicts
0xb0fbaf18…1c86
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xd9f18d9a…141d
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)
15 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity