← previous blocknext block →recent activity
Analyzing
Block #110,210,310
13 transactions · 11 stateful · 2026-10-03 14:59:37 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,210,310 · 13 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
2w03w16w29w310w412w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3483764…f29d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xdb7821c9…2e7b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0058
0x1b6862…e19c
6 touches
3 conflicts
0x1d5648b1…c329
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 0xc34837646d…35f29d
Audit this contract →
← previous block·next block →recent activity