← previous blocknext block →recent activity
Analyzing
Block #110,379,721
24 transactions · 21 stateful · 2026-10-04 05:12:03 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,379,721 · 24 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
1w02w13w24w35w48w39w415w016w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x9256b810…52c9
0x1b6862…e19c
10 touches
10 conflicts
0x5ea5543b…abd8
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0053
0x1b6862…e19c
6 touches
3 conflicts
0x9f574577…d84f
0x1b6862…e19c
6 touches
3 conflicts
0xece39774…e10f
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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity