← previous blocknext block →recent activity
Analyzing
Block #107,812,320
35 transactions · 27 stateful · 2026-09-25 05:42:14 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,812,320 · 35 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
1w02w13w24w316w017w319w431w032w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4caa
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
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
0xb00d1794…56d0
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…00001f
Audit this contract →
← previous block·next block →recent activity