← previous blocknext block →recent activity
Analyzing
Block #110,386,472
19 transactions · 16 stateful · 2026-10-04 05:46:01 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #110,386,472 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w011w013w114w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45364cf9…65d3
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x156f5ee9…0f67
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…0009
0x125f12…a50b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x40e44dcb…5ac9
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)
10 conflicts on slot 0x45364cf92a…4a65d3
Audit this contract →
← previous block·next block →recent activity