← previous blocknext block →recent activity
Analyzing
Block #110,380,342
20 transactions · 19 stateful · 2026-10-04 05:15:11 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,380,342 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w014w015w116w217w318w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3483764…f298
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3167beca…16fc
0xd32edf…ff58
7 touches
6 conflicts
0x1d5648b1…c329
0x1b6862…e19c
4 touches
1 conflict
0x9e9a67c9…e68e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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…35f298
Audit this contract →
← previous block·next block →recent activity