← previous blocknext block →recent activity
Analyzing
Block #109,176,984
22 transactions · 20 stateful · 2026-09-30 00:18:10 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,176,984 · 22 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
1w02w13w24w35w06w17w28w09w110w211w314w419w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xee44a19b…7571
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb3
0x1b6862…e19c
8 touches
6 conflicts
0x9047d0f1…01a0
0xd32edf…ff58
7 touches
6 conflicts
0xb8394f3d…8f29
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…000013
Audit this contract →
← previous block·next block →recent activity