← previous blocknext block →recent activity
Analyzing
Block #110,380,255
13 transactions · 12 stateful · 2026-10-04 05:14:44 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,380,255 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6235638c…6438
0x1b6862…e19c
6 touches
3 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x4c2b6b72…1387
0xd32edf…ff58
5 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)
3 conflicts on slot 0x6235638cfd…ef6438
Audit this contract →
← previous block·next block →recent activity