← previous blocknext block →recent activity
Analyzing
Block #108,681,939
23 transactions · 20 stateful · 2026-09-28 06:39:32 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,681,939 · 23 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
1w02w13w24w311w013w414w118w319w420w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0e4f69d…34e1
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xa8cec02b…2812
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x64ba89ac…2d82
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0xb0e4f69d8e…c534e1
Audit this contract →
← previous block·next block →recent activity