← previous blocknext block →recent activity
Analyzing
Block #109,133,907
18 transactions · 18 stateful · 2026-09-29 20:40:59 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,133,907 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w19w412w513w614w716w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc6a8c250…737a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xa3ee2156…2623
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0052
0x1b6862…e19c
6 touches
3 conflicts
0x6bfb0678…9860
0x1b6862…e19c
6 touches
3 conflicts
0xa9c1b1d5…5e4b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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…000015
Audit this contract →
← previous block·next block →recent activity