← previous blocknext block →recent activity
Analyzing
Block #110,329,196
20 transactions · 15 stateful · 2026-10-04 00:57:52 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,329,196 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w414w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xe4c6b0cb…0a20
0x1b6862…e19c
10 touches
10 conflicts
0xbb387263…d1c0
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x5274371f…a348
0x1b6862…e19c
8 touches
6 conflicts
0x59c73b7a…d846
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity