← previous blocknext block →recent activity
Analyzing
Block #100,984,835
24 transactions · 23 stateful · 2026-09-01 07:39:55 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,984,835 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w011w112w013w115w316w217w018w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda6b535e…6d6d
0x1b6862…e19c
8 touches
6 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x164833e5…8c01
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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)
6 conflicts on slot 0xda6b535e6c…386d6d
Audit this contract →
← previous block·next block →recent activity