← previous blocknext block →recent activity
Analyzing
Block #110,321,680
28 transactions · 25 stateful · 2026-10-04 00:20:03 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #110,321,680 · 28 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
1w02w13w24w35w46w57w68w721w322w425w727w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3af0dd8e…0022
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x39c6174f…f75e
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0052
0x1b6862…e19c
14 touches
21 conflicts
0x086626ee…2ad1
0x1b6862…e19c
14 touches
21 conflicts
0x5fd6ff96…b749
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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)
28 conflicts on slot 0x3af0dd8efa…df0022
Audit this contract →
← previous block·next block →recent activity