← previous blocknext block →recent activity
Analyzing
Block #109,229,088
15 transactions · 14 stateful · 2026-09-30 04:40:25 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,229,088 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w19w210w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xc6a8c250…737c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x3662cbcb…73f2
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0054
0x1b6862…e19c
6 touches
3 conflicts
0x6bfb0678…9862
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)
6 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity