← previous blocknext block →recent activity
Analyzing
Block #108,103,315
31 transactions · 30 stateful · 2026-09-26 06:06:50 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,103,315 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w715w116w217w322w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x6d43ee99…bdd7
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xdbe00f46…71f1
0xd32edf…ff58
15 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
12 touches
15 conflicts
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
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