← previous blocknext block →recent activity
Analyzing
Block #109,233,899
25 transactions · 23 stateful · 2026-09-30 05:04:37 UTC
Parallelism
56/100
Blocked
61%
Avg conflicts / tx
1.28
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #109,233,899 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w38w09w111w412w514w616w420w724w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xd18a8dca…452c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x2a5be21a…b8af
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0054
0x1b6862…e19c
8 touches
6 conflicts
0xa5b7d750…53dd
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity