← previous blocknext block →recent activity
Analyzing
Block #108,680,623
14 transactions · 13 stateful · 2026-09-28 06:32:53 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,680,623 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w59w010w112w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6235638c…6436
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0028
0x1b6862…e19c
12 touches
15 conflicts
0x300d6712…ac35
0xd32edf…ff58
11 touches
15 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)
15 conflicts on slot 0x6235638cfd…ef6436
Audit this contract →
← previous block·next block →recent activity