← previous blocknext block →recent activity
Analyzing
Block #109,133,824
34 transactions · 32 stateful · 2026-09-29 20:40:34 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,133,824 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w09w110w013w115w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bd55803…5d49
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x0a317a1f…35f9
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0052
0x1b6862…e19c
12 touches
15 conflicts
0x2cc82ae4…16cd
0x1b6862…e19c
12 touches
15 conflicts
0xd366dec4…a7f2
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 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)
21 conflicts on slot 0x3bd558039d…705d49
Audit this contract →
← previous block·next block →recent activity