← previous blocknext block →recent activity
Analyzing
Block #108,923,629
13 transactions · 11 stateful · 2026-09-29 02:59:23 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,923,629 · 13 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
1w02w13w24w310w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd59f6ed1…03e9
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x675a35ba…51f1
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0056
0x1b6862…e19c
6 touches
3 conflicts
0x15427cff…e8f9
0x1b6862…e19c
6 touches
3 conflicts
0x762d6568…db1e
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 0xd59f6ed156…8003e9
Audit this contract →
← previous block·next block →recent activity