← previous blocknext block →recent activity
Analyzing
Block #110,308,038
17 transactions · 15 stateful · 2026-10-03 23:11:25 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,308,038 · 17 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
1w02w13w24w35w49w010w112w014w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1526c23…f2b5
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xe2839874…5ad4
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0052
0x1b6862…e19c
8 touches
6 conflicts
0x48f92a13…4a06
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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 0xb1526c23fd…dbf2b5
Audit this contract →
← previous block·next block →recent activity