← previous blocknext block →recent activity
Analyzing
Block #109,230,479
18 transactions · 18 stateful · 2026-09-30 04:47:25 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2.44
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,230,479 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w815w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11998eac…f9a2
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x0b2efa51…8ed3
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0054
0x1b6862…e19c
16 touches
28 conflicts
0x09d0c090…d60d
0x1b6862…e19c
16 touches
28 conflicts
0x9baac2d0…4c1d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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)
36 conflicts on slot 0x11998eac41…19f9a2
Audit this contract →
← previous block·next block →recent activity