← previous blocknext block →recent activity
Analyzing
Block #107,803,689
30 transactions · 25 stateful · 2026-09-25 04:58:48 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,803,689 · 30 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
3w04w15w26w312w213w317w018w128w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x0747620e…9784
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x58418430…3ebb
0xd32edf…ff58
7 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)
6 conflicts on slot 0x0000000000…00002e
Audit this contract →
← previous block·next block →recent activity