← previous blocknext block →recent activity
Analyzing
Block #109,229,250
23 transactions · 21 stateful · 2026-09-30 04:41:14 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,229,250 · 23 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
1w02w13w24w35w46w310w011w112w213w317w119w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xf4713dd8…1579
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0054
0x1b6862…e19c
8 touches
6 conflicts
0x57d3b231…a40f
0x1b6862…e19c
8 touches
6 conflicts
0xb8394f3d…8f29
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 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)
10 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity