← previous blocknext block →recent activity
Analyzing
Block #100,878,138
21 transactions · 18 stateful · 2026-08-31 22:43:13 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,878,138 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w19w214w115w217w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aa624fd…a84f
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x5ef3f1f3…54b1
0xd32edf…ff58
11 touches
15 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)
15 conflicts on slot 0x6aa624fd35…14a84f
Audit this contract →
← previous block·next block →recent activity