← previous blocknext block →recent activity
Analyzing
Block #110,392,675
25 transactions · 23 stateful · 2026-10-04 06:17:14 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
2.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #110,392,675 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x928d6b23…536f
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x3dea4756…7713
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0053
0x1b6862…e19c
18 touches
36 conflicts
0x1aa19c07…50ed
0x1b6862…e19c
18 touches
36 conflicts
0xa7798c51…8be3
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 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)
45 conflicts on slot 0x928d6b23dd…ab536f
Audit this contract →
← previous block·next block →recent activity