← previous blocknext block →recent activity
Analyzing
Block #107,803,818
23 transactions · 23 stateful · 2026-09-25 04:59:27 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,803,818 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w010w111w112w213w414w315w416w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21d8e673…067f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xe96ff827…801a
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
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 0x21d8e67322…c7067f
Audit this contract →
← previous block·next block →recent activity