← previous blocknext block →recent activity
Analyzing
Block #100,854,717
25 transactions · 21 stateful · 2026-08-31 20:45:25 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,854,717 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w18w210w011w212w118w019w220w121w122w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba5743c7…21c2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
10 touches
10 conflicts
0x1684c28d…0d42
0xd32edf…ff58
9 touches
10 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 0xba5743c7a6…7321c2
Audit this contract →
← previous block·next block →recent activity