← previous blocknext block →recent activity
Analyzing
Block #109,142,948
38 transactions · 34 stateful · 2026-09-29 21:26:29 UTC
Parallelism
74/100
Blocked
65%
Avg conflicts / tx
1.92
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,142,948 · 38 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w220w824w132w433w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90d24713…b889
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0xd29a1fb5…ae4d
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0052
0x1b6862…e19c
14 touches
21 conflicts
0x2a63f37f…8c44
0x1b6862…e19c
14 touches
21 conflicts
0xaa38281e…0363
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
36 conflicts on slot 0x90d2471384…3bb889
Audit this contract →
← previous block·next block →recent activity